Русский
Українська
Հայերեն
ქართული
Қазақша
Español
Français
Deutsch
Italiano
فارسی
Article focus
A card payment is a chain of systems
The customer sees one checkout, while the merchant needs a reliable operational lifecycle.
The store creates an order and a controlled payment attempt, then sends the customer to checkout. The provider processes the selected card method and later returns a result that the backend must verify before changing the order.
This model applies whether a customer uses ArCa, Visa or Mastercard. The merchant should keep one internal status model while the acquiring provider handles the method-specific processing details.
- Create stable order and payment identifiers.
- Keep payment-method details behind the provider boundary.
- Verify final result on the backend.
Authentication and server-side status have different roles
3-D Secure helps authenticate a payment; it does not eliminate status verification.
Where applicable, 3-D Secure is part of the cardholder authentication journey. The customer-facing flow can be successful while a merchant backend still needs to obtain and validate the final provider status.
Do not mark an order paid from a browser return URL. Compare the verified amount, currency, order reference and final status with the expected payment attempt before releasing fulfilment.
- Treat authentication and settlement status separately.
- Validate amount and currency.
- Process callbacks idempotently.
Plan refunds and reconciliation from the start
Financial operations need the same traceable identifiers as checkout.
A completed payment is not the end of the lifecycle. Refunds, partial refunds, customer support and accounting reconciliation depend on a record that ties the provider reference to the original order and payment attempt.
Reconcile confirmed payments against provider and internal records on a planned schedule. Automatic status delivery is useful, but it does not replace an operational process for detecting mismatches or missed downstream events.
- Keep a payment and refund timeline.
- Reconcile provider and internal records.
- Audit manual resolution actions.
FAQ
Can ArCa and international cards use one checkout?
A supported acquiring product can present several card methods through one controlled checkout; confirm current methods with the provider.
Why is a success redirect not enough?
The backend still needs to verify the provider result before confirming an order.
Is reconciliation needed when callbacks are automatic?
Yes. Reconciliation detects mismatches between provider records and internal order, CRM or ERP data.
