Payment status defines the stage of transaction. The status can be transitional and final.
| ||Invoice has been created; processing has not started. If Corefy does not return response 201 (Created) HTTP status code on your request, you should admit that the payment invoice creation was failed.|
| ||✔||Invoice hit the lifetime limit without successful processing.|
| ||Process still being unknown and may not be known for an extended period.|
| ||✔*||Processed successfully. It isn't a final status since the payment can be refunded for different reasons.|
| ||✔||Processing has failed, may be set when an error occurs and the corresponding payment request has failed. This status is considered final due to the maximum number of attempts has been reached (default—after 5 attempts).|
| ||Refunding is still being unknown and may not be known for an extended period.|
| ||✔||Successfully refunded amount is less than the invoice amount.|
| ||✔||Successfully refunded in full.|
| ||✔||Refunding has been failed or cannot be completed.|
| ||✔||The payment transaction was claimed as a chargeback in full amount.|
| ||✔||The payment transaction was claimed as a chargeback but in amount less than the invoice amount.|
* — The status is considered as final, but the payment can be rejected for additional reasons or recovered (in refund or chargeback cases).
A resolution is a transaction status clarification.
With transitional and successful final statuses, the related resolutions have an
ok code. With failed final status, the resolutions get one of the following codes:
| ||The process completed successfully|
| ||Transaction is blocked by the provider's firewall|
| ||3D-Secure verification is required for processing|
| ||OTP verification is required for processing|
| ||The card authorisation failed|
| ||The card expired|
| ||3D-Secure verification is required for this card processing|
| ||The card is blocked because of the incorrect PIN using|
| ||The card is reported as lost|
| ||The card doesn't support 3D-Secure verification|
| ||The card is reported as stolen|
| ||Transaction processing on this card are restricted|
| ||The acquirer restricts transaction processing on this card|
| ||The card type is invalid|
| ||The card usage attempts limit is exceeded|
| ||The card usage issuer limit is exceeded|
| ||The card verification failed|
| ||The client authorisation failed|
| ||The customer isn't allowed to make this type of transactions|
| ||General decline|
| ||The transaction expired|
| ||Fatal decline|
| ||Fatal transaction processing error|
| ||The card is invalid and its re-using is forbidden|
| ||The transaction process is finalised manually|
| ||Insufficient funds|
| ||Invalid 3D-Secure verification code|
| ||Invalid transaction amount|
| ||The card is invalid|
| ||The cardholder name is incorrect|
| ||The card CVV is incorrect|
| ||The transaction details are incorrect|
| ||The card expiry date is incorrect|
| ||The OTP verification code is incorrect|
| ||General issuer decline|
| ||The card issuer is unavailable|
| ||The card limit is exceeded|
| ||Unable to determine the card 3D-Secure enrollment status|
| ||Unknown error|
The detailed level of the transaction's failure reason depends on the information openness of payment service providers (PSP) and issuer banks (for card transactions).
- Corefy could expand the list of resolutions lately.
- Receiving a resolution other than listed should not affect the transaction processing because this attribute only informs about possible errors.
- The finality and success of the transaction processing are determined solely by the payment status (
At different stages of the payment received, the identifiers are processed with different names. Check the relations between them in the diagram below.
Receiver Reference Number (RRN) and Acquirer Reference Number (ARN) are used only for card payments' identification.