Overview
The EasyPay integration connects payment events to Kapta Integrators, enabling automated invoicing, reconciliation, and operational workflows.
This integration is commonly used to synchronize payment confirmations with invoicing systems, update transaction statuses, and trigger subsequent financial processes without manual intervention.
Typical use cases
- Automatic invoice creation when a booking is confirmed
- Synchronization of customer and booking data with invoicing systems
- Propagation of payment status to operational tools
- Internal notifications for booking lifecycle events
Supported events
These events are issued by EasyPay and consumed by Kapta to trigger automated workflows.
The integration listens for the following EasyPay events:
- Payment initiated
- Payment confirmed
- Payment failed
- Refund processed
- Chargeback received
Data flow
The integration follows a predictable and auditable event-processing pipeline.
- EasyPay issues an event
- Kapta receives and validates the payload
- Data is normalized and mapped to internal models
- Workflows are executed based on configured rules
- Statuses and identifiers are synchronized across systems
Invoicing and payment behavior
When invoicing integrations are active, Kapta can:
- Create invoices automatically when a payment is confirmed
- Update invoice statuses based on payment or refund events
- Handle partial payments and refunds
- Maintain references between EasyPay transactions and invoicing documents
Setup
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 EasyPay and destination systems
- Rule definition for invoicing and workflow triggering
No client-side development is required.
Limitations
- Event delivery depends on the availability of the EasyPay API
- Some payment methods may have delayed confirmation
- Historical transactions may require a separate reconciliation process
Security and compliance
All data is transmitted securely through encrypted connections. Access is restricted to authorized systems and credentials are stored securely.
Invoicing and payment data is handled in compliance with Portuguese and European Union requirements, where applicable.
Frequently asked questions
Does this integration support multiple EasyPay accounts?
Yes. Multiple EasyPay accounts can be connected and isolated by integration.
Can workflows be customized 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 in near real time, depending on delivery by EasyPay.
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.
