ifthenpay | Payments for LatePoint

Descripción

This plugin integrates the ifthenpay payment gateway with LatePoint to enable seamless payment processing for appointment bookings. It supports multiple payment methods, including local options like Multibanco, MB WAY and Payshop, as well as international ones like PIX. Instant methods (MB WAY, cards, PIX, …) are handled via secure pay-by-link, with no sensitive card data stored on your site; Multibanco and Payshop are deferred — the customer gets a reference to pay at an ATM, via homebanking, or at a Payshop agent, and the booking confirms automatically once it’s paid. When a customer books an appointment, they can select their preferred payment method, and a secure payment page (or reference) is shown for completion.

In plain terms you get:
* One-time payments for bookings, instant or deferred (Multibanco, Payshop)
* Support for invoices and orders
* Merchant backoffice (basic sales) on web + mobile
* Secure automatic payment confirmations (no card numbers stored)
* An admin Tools page to recover a stuck payment without needing server access

Toda la configuración se realiza en LatePoint. El plugin está diseñado para que los propietarios de tiendas puedan gestionar los pagos sin necesitar conocimientos técnicos avanzados.

Características principales

  1. Integración sencilla con el flujo de reservas de LatePoint
  2. Pagos de facturas (asistencia para pedidos y facturas)
  3. Transacciones seguras mediante pay-by-link
  4. Deferred payment references (Multibanco, Payshop) with automatic slot release on expiry
  5. Confirmación automática de pago (acceso rápido)
  6. Múltiples tipos de pago locales (tarjetas, monederos, transferencias, vales)
  7. Backoffice para comerciantes (informes básicos de ventas y devoluciones)
  8. An admin Tools page: re-register the payment notification URL, recheck or cancel a stuck deferred payment, and review realtime payments that settled without a completed booking — all from wp-admin
  9. Seguridad ante todo (callbacks firmados, no se almacenan datos de tarjetas)

Requisitos

  • Una cuenta de comerciante activa de ifthenpay — suscríbete aquí para obtener tus credenciales.
  • A Static Gateway Key provisioned for the LatePoint context (request this from ifthenpay support/helpdesk).
  • Los métodos de pago que quieras activar en esa clave de pasarela (nuestro equipo de soporte te guiará).
  • WordPress 6.5+ and PHP 7.4+, and LatePoint 5.6+ installed and activated.
  • HTTPS (SSL) habilitado en tu sitio.
  • Outgoing email delivered reliably — many hosts block or throttle PHP’s default mail() function. An SMTP plugin (e.g. WP Mail SMTP) is recommended so the New Booking and Payment Received notifications actually reach customers and agents.

Servicios externos

Este plugin se integra con la plataforma de pagos de ifthenpay para procesar los pagos de las reservas de LatePoint. ifthenpay es un servicio de terceros que ofrece procesamiento seguro de pagos para varios métodos, incluidos tarjetas, monederos y transferencias bancarias locales.

  • LatePoint (plugin para reservar citas): ampliamos sus clases del marco de trabajo (OsFormHelper, OsSettingsHelper, etc.).
  • ifthenpay: Backoffice e integraciones
    • Qué es y para qué sirve: El Backoffice de ifthenpay es el panel de control del comerciante para gestionar las integraciones de pago. El plugin usa la API de ifthenpay para recuperar la configuración de la cuenta, generar enlaces de pago y procesar los pagos.
    • Qué datos se envían y cuándo:
    • Durante la configuración: Clave de Backoffice y Clave de Gateway (almacenadas de forma segura en los ajustes del sitio) para autenticar y obtener los métodos de pago disponibles.
    • Durante el procesamiento del pago: detalles mínimos de la transacción, incluidos el ID de transacción, el importe y los detalles de la reserva, para generar referencias de pago.
    • Acuerdo de licencia de usuario final (EULA): EULA
    • Política de privacidad: Política de privacidad
  • Network & VPN Requirements: Outbound HTTPS requests are made to ifthenpay APIs for setup, link generation, and status validation. Servers behind strict firewalls or restrictive outbound VPNs must allowlist the following domains to prevent connection timeouts:
    • api.ifthenpay.com (https://api.ifthenpay.com)
    • ifthenpay.com (https://ifthenpay.com)
  • Inbound callback URL: ifthenpay itself calls back to https://your-site.com/wp-json/ifthenpay-lp/v1/callback to confirm a payment. A site behind its own WAF, security plugin, or reverse proxy must allow GET requests to that path from ifthenpay’s servers, or payment confirmations will not arrive.

Todas las solicitudes de red se realizan del lado del servidor mediante HTTPS. Las credenciales sensibles se almacenan en las opciones del sitio y no se exponen públicamente. El plugin no almacena números de tarjeta en bruto ni datos bancarios completos.

Licencia

Este plugin está bajo licencia GPLv3.

Soporte

Si necesitas ayuda, utiliza el foro de soporte de WordPress.org:

Por favor, incluye:
* Cuenta de Backoffice
* URL del sitio web + versión del plugin
* Mensaje de error exacto + extractos relevantes del registro o capturas de pantalla

Comprobaciones previas a la publicación:
* Método de pago habilitado en Gateway Key Y asociado a la integración
* Se están utilizando las versiones actuales recomendadas de WordPress, PHP y LatePoint

Servicio de asistencia comercial disponible (no es necesario enviar un correo electrónico directamente): helpdesk.ifthenpay.com
* Asistencia de ifthenpay: suporte@ifthenpay.com
* Documentación de LatePoint: Documentación de LatePoint

Capturas

Instalación

  1. En el panel de administración de WordPress, ve a Plugins Añadir nuevo y busca ifthenpay | Payments for LatePoint; a continuación, haz clic en Instalar ahora.
  2. O bien, descarga ifthenpay-payments-for-latepoint.zip y súbelo en Plugins Añadir nuevo Subir plugin.
  3. Activa LatePoint y ifthenpay para LatePoint.
  4. Ve a LatePoint Ajustes Pagos, introduce tu clave de Backoffice y tu clave de pasarela de ifthenpay, y haz clic en Conectar.

FAQ

¿Qué necesito para empezar?

  • Una cuenta válida de ifthenpay (regístrate en ifthenpay.com/aderir)
  • LatePoint 5.6+ active
  • WordPress 6.5+ y PHP 7.4+

How do I get my Backoffice Key?

Your Backoffice Key is assigned by ifthenpay at the time your contract is validated at ifthenpay.com/aderir — it’s the same key used by ifthenpay’s other website and app integrations. If you don’t have it — setting up a new site, or you’ve lost it — ifthenpay support is who can resend it.

How do I get a Gateway Key for LatePoint?

A Gateway Key must be provisioned specifically for the LatePoint context before this plugin can use it — a Gateway Key created for a different platform (e.g. a generic website or another CMS) will not appear here, even with a valid Backoffice Key. Ask ifthenpay support to provision a Gateway Key for LatePoint on your account, then pick which payment methods (Multibanco, MB WAY, Payshop, cards, …) should be enabled on it — they’ll guide you through activation for each. Once that’s done, the plugin’s settings page picks it up automatically; there is nothing to enter by hand beyond the Backoffice Key itself.

¿Cómo lo configuro?

  1. Ve a LatePoint Ajustes Pagos.
  2. Enter your Backoffice Key and click Connect — this checks it against ifthenpay and shows your available Gateway Key(s).
  3. Pick a Gateway Key, select the payment methods (including invoices) you want to offer, then save.
  4. Save again any time you change the Gateway Key — this also re-registers the payment notification (callback) URL ifthenpay uses to confirm a payment automatically; see below.

Does ifthenpay need access back into my site?

Yes — after a Gateway Key is saved, the plugin registers a payment notification URL with ifthenpay (https://yoursite.com/wp-json/ifthenpay-lp/v1/callback) so a payment can be confirmed automatically once it’s completed. This happens automatically; there’s nothing to copy or paste. If your server sits behind a firewall, WAF, or security plugin that blocks unfamiliar inbound requests, allow GET requests to that URL path through — otherwise a completed payment may not be confirmed automatically. If registration itself fails (for example, your site isn’t reachable from the internet yet), the settings page shows which Gateway Key failed and why, without needing to re-enter anything.

¿Cómo funciona el proceso de pago?

Los pagos se procesan de forma segura mediante el sistema de pay-by-link de ifthenpay. Los clientes seleccionan un método de pago durante la reserva, y se abre una página de pago segura para completar la transacción. Una vez pagado, el estado se verifica y la reserva se confirma automáticamente.

How does Multibanco payment work?

Multibanco is deferred, not instant: at checkout the customer gets an Entity/Reference/Amount to pay at an ATM or via homebanking, instead of a card-style payment page. The booking is created right away — pending, not confirmed — and the reference is shown on the confirmation page, in the confirmation email, and later in the customer’s dashboard, so it isn’t lost. The booking confirms automatically once ifthenpay notifies the site the reference was paid, typically within minutes of payment.

How does Payshop payment work?

Payshop works the same way as Multibanco: a deferred reference, shown at checkout, in the confirmation email, and on the customer’s dashboard, payable in person at any Payshop agent or CTT post office. The booking is created pending and confirms automatically once ifthenpay notifies the site it was paid.

What happens if a Multibanco or Payshop reference is never paid?

The booking still holds the time slot while the reference is pending — nobody else can book it in the meantime, so an unpaid reference blocks that slot until it expires. An hourly job cancels bookings whose reference has passed its validity window, releasing the slot back for others to book. Set how many days a reference stays valid, and the minimum lead time before an appointment a reference can still be issued for, under LatePoint Settings Payments Pay Later Configuration [Multibanco/Payshop] Timing. Each agent also gets a daily email listing their own appointments whose reference lapsed unpaid, so nothing falls through unnoticed.

A customer says they paid a Multibanco or Payshop reference but the booking still shows pending — what do I do?

This is rare (a network hiccup between ifthenpay and your site), but recoverable without touching the database or a server. Go to Settings ifthenpay for LatePoint in wp-admin — the Outstanding Deferred Payments table lets you Recheck a specific payment (confirms it with ifthenpay directly before settling anything, so it’s safe to run even if the payment never actually completed) or Cancel it to release the slot.

A customer paid instantly (MB WAY, card, …) but no booking shows up — where did the money go?

This can happen if the customer’s connection dropped right after paying, before their booking could be finalised. Go to Settings ifthenpay for LatePoint in wp-admin and check the Unclaimed Realtime Payments table — it lists any payment that was confirmed paid by ifthenpay but never matched to a completed booking, along with whatever contact and booking details were captured at checkout, so you can follow up with the customer directly. Mark a payment Resolved once you’ve handled it with them; if you did that by mistake, the Resolved tab lets you undo it.

¿Se almacenan los datos de pago?

No. El plugin no almacena números de tarjeta ni datos bancarios completos. Solo se conservan pequeñas referencias necesarias para la conciliación de pagos.

¿Existe un entorno de pruebas?

ifthenpay puede ofrecer entidades de prueba; si no está disponible, usa una prueba real de bajo valor.

¿Qué métodos de pago se admiten?

Cualquier método de ifthenpay asociado a tu Clave de Gateway (p. ej., Multibanco, MB WAY, Payshop, Pix, Tarjeta de crédito si está habilitada).

¿Qué tan segura es la integración?

Las solicitudes se cifran mediante HTTPS; los datos se minimizan; no se almacenan datos de tarjetas. Los pagos son gestionados fuera de tu sitio por ifthenpay, lo que garantiza el cumplimiento de PCI.

¿Por qué fallan los enlaces de pago o se agota el tiempo de configuración?

El firewall de tu servidor o una VPN pueden estar bloqueando las solicitudes salientes. El plugin necesita conectarse con las API de ifthenpay para funcionar. Asegúrate de que tu administrador de red permita el tráfico HTTPS saliente hacia los dominios de ifthenpay.

A booking or payment confirmation email never arrived — is that this plugin?

Usually not a payment problem — check who was actually supposed to get it. LatePoint’s own New Booking Notification workflow emails both the agent («New Appointment Received») and the customer («Appointment Confirmation») when a booking is made. The Payment Received workflow this plugin adds emails the customer only, once payment settles — an order can span bookings with different agents, so there’s no single agent to notify there. Both live under LatePoint Automation Workflows and both send through WordPress’s own mail function; if your host doesn’t relay mail reliably (common on shared hosting), they silently fail to send — install and configure an SMTP plugin (e.g. WP Mail SMTP) with a real mail provider. Either way, the booking status and any Multibanco/Payshop reference are always also shown on-screen at checkout and in the customer’s LatePoint dashboard, so a missing email doesn’t put the payment itself at risk.

Reseñas

No hay valoraciones para este plugin.

Colaboradores y desarrolladores

«ifthenpay | Payments for LatePoint» es un software de código abierto. Las siguientes personas han colaborado con este plugin.

Colaboradores

«ifthenpay | Payments for LatePoint» está traducido en 1 idioma. Gracias a los traductores por sus contribuciones.

Traduce «ifthenpay | Payments for LatePoint» a tu idioma.

¿Interesado en el desarrollo?

Revisa el código , echa un vistazo al repositorio SVN o suscríbete al registro de desarrollo por RSS.

Registro de cambios

3.0.0

  • Added: Multibanco as a deferred payment method — the customer gets an Entity/Reference/Amount at checkout to pay at an ATM or via homebanking, and the booking confirms automatically once ifthenpay reports it paid.
  • Added: Payshop as a deferred payment method — works like Multibanco, but is paid in person at any Payshop agent or CTT post office.
  • Added: Per-method Pay Later Configuration (Reference Validity in days, minimum lead time before an appointment) for Multibanco and Payshop, each clamped so a reference is never issued longer than the appointment allows.
  • Added: An hourly job cancels bookings whose Multibanco or Payshop reference lapsed unpaid and releases the slot; each agent also gets a daily digest email of their own lapsed-unpaid appointments.
  • Added: A new Tools page (Settings ifthenpay for LatePoint) to re-register the callback URL, recheck or cancel a stuck deferred payment, and review realtime payments that settled without a matching booking — all from wp-admin, no server access required.
  • Added: A «Payment Received» notification is now seeded automatically under LatePoint Automation Workflows on activation, so the customer automatically gets a payment confirmation email without the merchant building one by hand.
  • Changed: Backoffice Key and Gateway Key configuration reworked — the Backoffice Key is now validated against ifthenpay directly when you save it, and the Gateway Key list and available payment methods are read live instead of cached from a separate «Connect» step.
  • Changed: The callback URL ifthenpay uses to confirm payments is now registered automatically whenever you save a Gateway Key, with the result shown on the settings page if it fails.
  • Changed: ifthenpay payment methods are no longer offered at checkout unless the saved Gateway Key is currently valid, even if the processor itself is turned on.
  • Fixed: Payment records now use one shared table instead of a single-purpose one; existing history is kept, not deleted, during the update.

2.1.1

  • Changed: Payment charge reference is now the payment token instead of the ifthenpay transaction ID, so merchants can reconcile payments more easily.
  • Fixed: Increased the payment status verification timeout from 10s to 45s to give slower payment methods enough time to confirm before giving up.
  • Fixed: Applied WPCS (PHPCBF), ESLint, and Prettier formatting baseline across the plugin (tabs, single quotes, WPCS spacing).

2.1.0

  • Corregido: actualizada la lista blanca de acceso público en el controlador para usar los nombres de método correctos (get_order_ifthenpay_options, get_transaction_ifthenpay_options) en lugar del obsoleto get_ifthenpay_options.
  • Corregido: eliminado get_payment_options, que no existía, de la lista blanca de acceso de clientes.

2.0.5

  • Actualizado: actualizado «Tested up to» a WordPress 6.9 en todos los archivos relevantes.
  • Añadido: filtrado de métodos invisibles.

2.0.3

  • Corregido: nomenclatura genérica de clases e ineficiencias.
  • Corregido: añadido el prefijo ‘Ifthenpay’ a la clase estática ‘AdminFormRenderer’.
  • Corregido: depurada la lógica de limpieza de ajustes y mejorado el manejo del estado de error en el controlador.
  • Corregido: eliminado el ifthenpay_nonce no utilizado de las variables localizadas y las llamadas AJAX de JavaScript.

2.0.1

  • Corregido: correcciones de versionado y eliminación del innecesario ‘load_plugin_text_domain’.

2.0.0

  • Añadido: Compatibilidad con el pago de facturas (Pedidos y facturas).
  • Cambiado: aclarado el requisito de cuenta de ifthenpay y el enlace de suscripción.

1.0.0

  • Primera versión estable.