Payment Statuses & Resolutions

Status is an element tracks a payment throughout its entire lifecycle. It provides real-time visibility into the current stage of the transaction, allowing users to monitor its progress from start to finish.

Resolution represents the definitive outcome or final state of a specific payment stage. It serves as an immediate confirmation of how that particular phase was resolved.

Payment Request (PR)

A Payment Request is the core entity that triggers the transaction process. It is created to represent the transaction on the Merchant's side and acts as the official starting point whenever a Merchant initiates a new payment.

Payment Request statuses

Status	Description
created	Payment Request is successfully created. Initial status.
failed	Final failed status resulting from: termination — cancellation of the created request by the merchant; retry limit — user payment attempts have expired; expiration — the request lifespan has expired.
expired	PR has expired and is no longer valid.
attempted	A payment attempt was made — a Payment Commit was created (the payer interacted with the checkout) and it is still either in pending or unsuccessful.
pending	At least one PC has a successful financial transaction and: the PC amount does not fully cover the PR and the lifespan has not expired yet; the amount is captured and PR awaits further cancellation/capture interaction within the delayed_charge type; the amount is captured and a return or confirmation is made for the verify type.
paid	PR has been paid in full, but funds can be returned at the request of the Merchant (refund) or by the bank (chargeback).
partially_paid	PR has been paid partially.
partially_returned	The funds have been returned partially at the request of the Merchant.
returned	The funds have been returned in full at the request of the Merchant.
verified	The payer's Payment account (card/wallet) has been successfully verified.
cancelled	PR was canceled by the Merchant (funds were returned to the payer’s account) within the delayed charge type.
over_paid	PR has been paid, and the amount for the transactions exceeds the original payment amount.

Payment Request resolutions

Resolution	Description
ok	The process completed successfully.
expired	The Payment Request has expired.
attempt_limit_reached	The defined Attempt limit has been reached.
merchant_account_disabled	The given Merchant account has been disabled.
organization_disabled	The given Organisation has been disabled.

Payment Commit (PC)

PC is an entity that confirms a Customer's intent to move forward with a transaction. Its role is to ensure the payment is verified, allowing for the subsequent allocation of funds.

Payment Commit statuses

Status	Description
created	Payment Commit has been created.
authorize_pending	Payment Commit awaits the payment interaction.
authorize_failed	Payment Commit did not pass the payer data check.
authorized	Payment Commit passed the payer data check.
void_pending	Payment Commit is in the process of returning.
voided	Payment Commit is returned to the account.
capture_pending	Payment Commit is in the process of being credited.
captured	Payment Commit is paid.
refund_pending	Funds are in the process of being returned via a Refund.
refunded	Funds have been fully refunded via Refund payment.
partially_refunded	Funds have been partially refunded via Refund payment.
charged_back	Funds have been fully refunded via Chargeback payment.
partially_charged_ back	Funds have been partially refunded via Chargeback payment.

Payment Commit resolutions

Resoution	Description
ok	The process was completed successfully.
payment_expired	The payment has been expired.
transaction_limit_reached	The Transaction limit has been reached.
payment_hard_declined	The Payment Commit is terminated by Firewall rules.
processing_error	The system errors occurred.
terminated_by_trigger_rules	The Payment Commit is terminated by the Trigger rules.
terminated_by_routing_rules	The Payment Commit is terminated by the Routing rules.
no_available_routes _for_selected_method	Payment routes are not enabled for the current method. Check the method and route settings.
no_routes_by_failure_history	No routes were found as the routes were not defined due to the history errors.
no_routes_by_conditions	The routes are not set up based on the rules.
no_routes_by_payment _route_amount_limits	There are no routes with available payment limits (each route has its own payment limit).
no_routes_by_merchant _account_amount_limits	There are no routes with available payment limits if limits are set at the Merchant level for the minimum and maximum amount.
no_routes_by_turnover_limits	There are no routes available due to turnover limits being reached
no_routes_by_processing_options	There are no routes for processing options (e.g. hard 3ds, OTP, etc.).
no_routes_by_payment _request_flow	No routes are available due to errors in the Payment Request process.
no_routes_by_strategy_options	There are no routes in a Routing strategy.
no_routes_by_fields	There are no routes available through filled fields.
strategy_specified _routes_pre_filtered	The strategy identifies routes that have passed preliminary filtering.
strategy_received_no_routes	The strategy could not find any routes.
strategy_returns_no_routes	The strategy could not find any routes.
filter_received_no_routes	Filtering did not return any routes.
no_routes_by_enabled_ provider_account_payment_gateway	The error occurred at the Provider account level.
no_routes_by_enabled _provider_account	The route is switched off at the Provider level.
refund_failed	The system failed to process a Refund due to some technical reasons.