AaaS Resources

This section provides reference data and enumerations used in the payment workflow, including test cards, order types, order statuses, dispute information and error code reference.


1. Test Card

The following test card numbers can be used in the sandbox environment for payment testing.

Card typeTest card number
Maestro6759649826438453
Mastercard5555555555554444 5454545454545454 2221000000000009
Mastercard Debit5163613613613613
Visa4444333322221111 4911830000000 4917610000000000
Visa Debit4462030000000000 4917610000000000003


2. Order Type

The following order types are used to identify the purpose of each transaction.

Enum ValueDescription
PAYMENTNormal payment order (customer pays merchant for goods/services)
REFUNDRefund order (merchant refunds the customer for a previously paid order)


3. Order Status

The following order statuses indicate the current state of a payment or refund during its lifecycle.

Enum ValueDescription
PENDINGOrder created, being processed (initial status)
READYOrder processed successfully, waiting for customer payment
PAIDCustomer has paid successfully, order completed
FAILEDOrder processing failed (e.g., gateway error, parameter error)
CANCELEDOrder canceled (initiated by the merchant or customer via the cancel interface)
REFUNDEDOrder has been fully refunded
CANCELINGOrder cancellation is in progress (intermediate status)
AUTHORIZEDPayment has been authorized (for pre-authorization scenarios)
REFUNDINGRefund is in progress (intermediate status)
CAPTUREDAuthorized amount has been captured (for pre-authorization capture scenarios)
CLOSEDOrder closed (usually due to expiration without payment)


4. Dispute Case Type

The following dispute case types classify different stages and categories of dispute or chargeback events.

Enum ValueDescription
FIRST_CHARGEBACKInitial chargeback initiated by the issuing bank on behalf of the cardholder (the first formal dispute for a transaction).
SECOND_CHARGEBACKSecondary chargeback raised by the issuing bank if the merchant successfully overturns the first chargeback (requires new evidence from the issuing bank).
RAPID_DISPUTE_RESOLUTIONFast-track dispute process (RDR) - Used for low-value or clear-cut disputes to resolve issues quickly without formal chargeback procedures.
RETRIEVALRequest from the issuing bank to retrieve transaction documentation (e.g., receipts, order confirmations) - May precede a formal chargeback if documentation is insufficient.


5. Dispute Case Status

The following dispute case statuses describe the current progress of a dispute throughout its resolution process.

Enum ValueDescriptionMerchant Action Required
NOTICEDispute notification sent to the merchant (case has been opened).Yes - Review dispute details, prepare evidence, and submit before dueDate.
REPRESENTATIONThe merchant has submitted evidence; the case is pending review.No - Wait for the issuing bank/card network to issue a ruling.
ISSUER_PENDINGThe case is under review by the issuing bank.No - No action required until a ruling is made.
CB_DISPUTE_WINThe merchant has won the dispute; funds will be returned.No - Confirm fund receipt (system will process automatically).
CB_DISPUTE_LOSSMerchant has lost the dispute; funds will be deducted.No - Review the ruling and adjust internal processes if needed.
AGREE_CBThe merchant has agreed to the dispute (no evidence submitted).No - Case will be closed as "lost" automatically.
CANCELDispute has been canceled (e.g., initiated in error).No - No further action required.
CLOSEDDispute process is fully completed (final status).No - Case is archived; no additional updates.


6. Error Code Reference

The following error codes describe errors that may occur during payment processing and related operations.

TypeCodeMessageHTTP Status
General150001Unable to process the request400 BAD_REQUEST

TypeCodeMessageHTTP Status
Request Parameters151001Invalid request parameters400 BAD_REQUEST
Request Parameters151002The payment method is required in direct mode400 BAD_REQUEST
Request Parameters151003Country is required400 BAD_REQUEST
Request Parameters151004State or province is required400 BAD_REQUEST
Request Parameters151008Success and failure URLs are required for redirect payments400 BAD_REQUEST
Request Parameters151009Invalid URL400 BAD_REQUEST
Request Parameters151010Amount for %s must have at most %d decimal places400 BAD_REQUEST

TypeCodeMessageHTTP Status
Card Information151101Card information is required400 BAD_REQUEST
Card Information151102Invalid card number400 BAD_REQUEST
Card Information151103Invalid card expiration date400 BAD_REQUEST

TypeCodeMessageHTTP Status
Merchant Configuration153101This payment method is not enabled for your account400 BAD_REQUEST
Merchant Configuration153102No payment methods are enabled for your account400 BAD_REQUEST
Merchant Configuration153103Direct payments are not enabled for your account400 BAD_REQUEST
Merchant Configuration153104Redirect payments are not enabled for your account400 BAD_REQUEST
Merchant Configuration153105No matching payment configuration was found400 BAD_REQUEST
Merchant Configuration153106Payment method %s does not support transaction type %s400 BAD_REQUEST
Merchant Configuration153107Transaction type %s is not enabled for your account400 BAD_REQUEST
Merchant Configuration153108Currency %s is not supported by your account400 BAD_REQUEST

TypeCodeMessageHTTP Status
Payment Service154001Payment service is temporarily unavailable503 SERVICE_UNAVAILABLE
Payment Service154002Payment service is temporarily unavailable503 SERVICE_UNAVAILABLE
Payment Service154003This payment method is not supported503 SERVICE_UNAVAILABLE

TypeCodeMessageHTTP Status
Order155001Order not found400 BAD_REQUEST
Order155003Order has expired400 BAD_REQUEST
Order155004Payment not found400 BAD_REQUEST
Order155005Merchant order number %s already exists400 BAD_REQUEST
Order155006Merchant customer ID is required400 BAD_REQUEST
Order155007Transfer reference is required for an AFT transaction400 BAD_REQUEST
Order155008Unable to create the payment address400 BAD_REQUEST

TypeCodeMessageHTTP Status
Payment Result155101Payment declined400 BAD_REQUEST
Payment Result155102Insufficient funds400 BAD_REQUEST
Payment Result155103Limit exceeded400 BAD_REQUEST
Payment Result155104Transaction not permitted400 BAD_REQUEST
Payment Result155105Authentication required400 BAD_REQUEST
Payment Result155106Authentication failed400 BAD_REQUEST
Payment Result155107Verification failed400 BAD_REQUEST
Payment Result155108Expired payment method400 BAD_REQUEST
Payment Result155109Invalid or unavailable account400 BAD_REQUEST
Payment Result155110Lost or stolen card400 BAD_REQUEST
Payment Result155111Security violation400 BAD_REQUEST
Payment Result155112Unable to authorise400 BAD_REQUEST
Payment Result155113Payment not supported400 BAD_REQUEST
Payment Result155114Policy reasons400 BAD_REQUEST
Payment Result155115Invalid security code400 BAD_REQUEST
Payment Result155116Invalid PIN400 BAD_REQUEST
Payment Result155117Allowable number of PIN tries exceeded400 BAD_REQUEST
Payment Result155118Closed account400 BAD_REQUEST
Payment Result155119Do not honour400 BAD_REQUEST

TypeCodeMessageHTTP Status
Refund Result155201Refund amount exceeds the original payment amount400 BAD_REQUEST
Refund Result155202Total refund amount exceeds the original payment amount400 BAD_REQUEST
Refund Result155203Another refund is already being processed for this payment400 BAD_REQUEST
Refund Result155204The original payment is not completed400 BAD_REQUEST
Refund Result155205Original payment not found400 BAD_REQUEST
Refund Result155206The payment has an active dispute and cannot be refunded400 BAD_REQUEST
Refund Result155207Insufficient available balance400 BAD_REQUEST
Refund Result155208The payment has already been fully refunded400 BAD_REQUEST
Refund Result155209Refund failed400 BAD_REQUEST

TypeCodeMessageHTTP Status
Risk Control156001Transaction declined400 BAD_REQUEST
Risk Control156002This card cannot be used400 BAD_REQUEST

Did this page help you?