Before installing a payment integration, decide how your business will recognize a successful payment and handle exceptions. That decision connects the customer experience to operations.
01 / Map the order lifecycle
Write down the transition from cart to order, invoice creation, payment detection and fulfillment. Keep the order reference attached to the invoice. Decide what happens when a customer closes the checkout or returns later.
02 / Define acceptance rules
Your payment system may distinguish detected, processing, settled, expired and invalid states. Map those states to business actions deliberately. A browser redirect alone is not evidence that an invoice was paid.
03 / Test the uncomfortable cases
Test expiry, partial payment, delayed confirmation, duplicate callbacks and interrupted connections in a controlled environment. Record the expected order state and customer message for each case.
04 / Prepare the daily workflow
Assign responsibility for reconciliation, support and refunds. Keep a written exception queue so unresolved payments do not disappear between the store, finance and support teams.
Planning guidance. Confirm procedures against your software version’s documentation and seek qualified support for your environment. Reviewed October 31, 2026.