03.04 Transaction Lifecycle and Statuses

Status: draft for discussion

1. Goal

Transaction statuses must be clear for merchants, platform users, and support.

It is important not to break the meaning of statuses that merchants are already used to.

2. MVP Statuses

• CREATED - transaction was created.
• PENDING_CUSTOMER_INPUT - the system is waiting for additional customer fields.
• WAITING_PROVIDER_RESULT - transaction is waiting for provider result, but this does not mean money has moved.
• PROCESSING - provider reported that payment is in processing, and merchant may accept business risk.
• COMPLETED - transaction succeeded.
• FAILED - transaction ended with an error.
• CANCELED - transaction was canceled or expired.
• REJECTED - transaction was rejected by our system for an internal business reason.

Exact technical status names can be proposed by the development team, but the business meaning must remain the same.

3. Final Statuses

Final statuses:

• COMPLETED;
• FAILED;
• CANCELED;
• REJECTED.

Final status cannot be changed automatically after it is set.

Manual correction can change final status if the user has the required business access.

4. Meaning of PROCESSING

PROCESSING must mean provider-side processing.

It is not just the fact that we sent a request to provider.

This matters because merchant can use PROCESSING as a signal that they accept business risk.

5. Expiration

Transaction and Hosted Payment Page must have expiration behavior.