Overview
The IfthenPay integration connects payment reference events to Kapta Integrators, enabling automated invoicing, reconciliation, and operational workflows.
This integration is typically used to synchronise Multibanco references and MB Way payments with invoicing systems, update transaction statuses, and trigger subsequent financial processes without manual intervention.
Typical use cases
- Automatically create invoices when a payment is confirmed
- Synchronise Multibanco and MB Way payment references with invoicing systems
- Propagate payment statuses to accounting and operational tools
- Send internal notifications for payment lifecycle events
Supported events
These events are issued by IfthenPay and consumed by Kapta to trigger automated workflows.
The integration listens for the following IfthenPay events:
- Payment reference generated
- Payment confirmed
- Payment expired
- Refund processed
Data flow
The integration follows a predictable and auditable event-processing pipeline.
- IfthenPay issues an event
- Kapta receives and validates the payload
- Data is normalised and mapped to internal models
- Workflows are run according to configured rules
- Statuses and identifiers are synchronised between systems
Invoicing and payment behaviour
When invoicing integrations are active, Kapta can:
- Create invoices automatically when a payment is confirmed
- Update invoice statuses based on payment, expiry, or refund events
- Handle partial payments and refunds
- Maintain references between IfthenPay transactions and invoicing documents
Configuration
Integrations are configured once and centrally maintained by Kapta.
Configuration is handled by the Kapta team and typically includes:
- API credential configuration
- Event selection and filtering
- Data mapping between IfthenPay and target systems
- Definition of invoicing rules and workflow activation
No client-side development is required.
Limitations
- Event delivery depends on the availability of the IfthenPay API
- Some payment methods may have delayed confirmation
- Historical payments may require a separate reconciliation process
Security and compliance
All data is transmitted securely through encrypted connections. Access is restricted to authorised systems, and credentials are stored securely.
Invoicing and payment data is handled in accordance with Portuguese and European Union requirements, where applicable.
Frequently asked questions
Does this integration support multiple IfthenPay accounts?
Yes. Multiple IfthenPay accounts can be connected and isolated per integration.
Can workflows be customised by product or activity?
Yes. Rules can be defined based on booking attributes, products, or payment status.
Is real-time processing supported?
Yes. Events are processed near real time, depending on delivery by IfthenPay.
Need help or changes?
This integration is managed by the Kapta team. If you need adjustments, additional events, or invoicing rules, contact support to discuss your requirements.
