Keep payment, fulfilment and refund states distinct
A payment integration must explain more than whether a transaction exists. We connect the accepted payment state to an invoice or order, handle partial and late payments and keep refunds as separately authorised operations. Supported networks and custody responsibilities are defined before development.
Amount differences
Define underpayment, overpayment and late-payment handling.
Refund authority
Specify destination verification and approval responsibilities.
Where it fits
Practical Use Cases
01
Project billing
Link accepted payments to existing invoices.
02
Commerce platforms
Trigger fulfilment only from verified payment events.