External Payment - Flow Descriptions
Information in this article is in preview status. Do not use information in this article without being in contact with Future Ordering.
This document describes the expected interaction patterns between Future Ordering and a Partner payment provider. It is intended to guide Partner integrations by defining the required request/response contracts, event delivery expectations, and timeout behaviours.
All payment operations are initiated by FO Payment System via an HTTP POST to a Partner-configured endpoint (shown as POST /payments in the diagrams below) and are completed asynchronously. The Partner responds with 202 Accepted and subsequently delivers a completion event to the FO Payment Notifications endpoint. The URL is configurable per merchant.
Standard Flow
Full Transaction Lifecycle
Complete flow from registration through authorization to capture.
Variants
User Cancellation During Registration
User cancels the payment while registration is being processed.
Annulment After Authorization
Authorization is annulled when order placement fails after a successful authorization.
Failure Scenarios
Validation Error
Partner rejects the request immediately with 400 Bad Request due to malformed JSON or a missing required field. No event is sent as the operation was never accepted.
Registration Failed
Partner accepts the registration but it fails downstream, e.g. the request to the payment provider times out.
Authorization Declined
Partner accepts the operation but the payment is declined downstream, e.g. by the card scheme.
Capture Failed
Partner accepts the capture but it fails downstream, e.g. the payment provider rejects the settlement.
Non-Retryable Capture Failure
Partner accepts the capture but it fails permanently downstream, e.g. due to a fiscalization error at the terminal. The capture cannot be retried. FO Payment System may retry the capture, but each attempt fails. When the reservation expires, FO Payment System sends an annulment to release the reserved funds.
Annulment Failed
Partner accepts the annulment but it fails downstream, e.g. the payment provider rejects the reversal.
Conflicting Operation
Partner accepts the operation but the transaction is in an incompatible state, e.g. a capture operation when the transaction is annulled.
Stalled Authorization
Partner accepts but never sends a completion event within the timeout window. FO Payment System transitions the payment to a failed state and sends an annulment request.
Unacknowledged Registration
The Partner completes registration but the event delivery to FO Payment Notifications fails. The Partner aborts the registration as a compensating action. FO Payment System receives no registration event and transitions the payment to a failed state on timeout.