A request is the beginning
A payment request should identify the intended amount, currency and business reference. An opened payment link only shows that someone viewed it. It does not establish that a payment completed.
The provider supplies the result
The integration needs to verify the payment provider’s server-side response using the selected provider’s documented process. A browser redirect is useful for the customer experience, but should not be the sole authority for updating an order.
Repeated messages are normal
Notifications can be delayed or delivered more than once. The application should recognise a previously processed event and avoid repeating fulfilment. A pending result should stay distinct from a failure or a confirmed payment.
Reconciliation completes the picture
Staff need to match the confirmed transaction to the invoice, order or booking. Clear references and a reviewable history make discrepancies easier to investigate. The exact settlement and reconciliation behaviour depends on the provider and merchant arrangement.
Try the whole journey
The Payment Link Studio uses fictional data to show creation, pending, failure, expiry, payment and reconciliation. It is a way to understand the workflow without entering card details or moving money.
Have a workflow in mind? Turn it into a useful starting brief.
Open the Solution Architect