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

1. Test Card

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

Card type	Test card number
Maestro	6759649826438453
Mastercard	5555555555554444 5454545454545454 2221000000000009
Mastercard Debit	5163613613613613
Visa	4444333322221111 4911830000000 4917610000000000
Visa Debit	4462030000000000 4917610000000000003

2. Order Type

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

Enum Value	Description
`PAYMENT`	Normal payment order (customer pays merchant for goods/services)
`REFUND`	Refund 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 Value	Description
`PENDING`	Order created, being processed (initial status)
`READY`	Order processed successfully, waiting for customer payment
`PAID`	Customer has paid successfully, order completed
`FAILED`	Order processing failed (e.g., gateway error, parameter error)
`CANCELED`	Order canceled (initiated by the merchant or customer via the cancel interface)
`REFUNDED`	Order has been fully refunded
`CANCELING`	Order cancellation is in progress (intermediate status)
`AUTHORIZED`	Payment has been authorized (for pre-authorization scenarios)
`REFUNDING`	Refund is in progress (intermediate status)
`CAPTURED`	Authorized amount has been captured (for pre-authorization capture scenarios)
`CLOSED`	Order 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 Value	Description
`FIRST_CHARGEBACK`	Initial chargeback initiated by the issuing bank on behalf of the cardholder (the first formal dispute for a transaction).
`SECOND_CHARGEBACK`	Secondary chargeback raised by the issuing bank if the merchant successfully overturns the first chargeback (requires new evidence from the issuing bank).
`RAPID_DISPUTE_RESOLUTION`	Fast-track dispute process (RDR) - Used for low-value or clear-cut disputes to resolve issues quickly without formal chargeback procedures.
`RETRIEVAL`	Request 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 Value	Description	Merchant Action Required
`NOTICE`	Dispute notification sent to the merchant (case has been opened).	Yes - Review dispute details, prepare evidence, and submit before `dueDate`.
`REPRESENTATION`	The merchant has submitted evidence; the case is pending review.	No - Wait for the issuing bank/card network to issue a ruling.
`ISSUER_PENDING`	The case is under review by the issuing bank.	No - No action required until a ruling is made.
`CB_DISPUTE_WIN`	The merchant has won the dispute; funds will be returned.	No - Confirm fund receipt (system will process automatically).
`CB_DISPUTE_LOSS`	Merchant has lost the dispute; funds will be deducted.	No - Review the ruling and adjust internal processes if needed.
`AGREE_CB`	The merchant has agreed to the dispute (no evidence submitted).	No - Case will be closed as "lost" automatically.
`CANCEL`	Dispute has been canceled (e.g., initiated in error).	No - No further action required.
`CLOSED`	Dispute process is fully completed (final status).	No - Case is archived; no additional updates.