Payment status

CONFIRMED

• Description: The payment is finalized. The buyer has been debited, and all beneficiaries have been credited.
• Typical Use Case: Occurs when sufficient funds are available and the payment has been successfully processed.

---

REFUSED

• Description: The payment was declined due to insufficient buyer funds or another issue preventing the transaction.
• Typical Use Case: Triggered when the buyer’s account does not have enough balance or authorization to complete the payment.

---

REIMBURSED

• Description: The buyer has been refunded, indicating the payment was reversed after initially being debited.
• Typical Use Case: Applied when a product/service is returned, canceled post-purchase, or otherwise requires reversing the payment.

---

CANCELLED

• Description: In a manually confirmed payment scenario, the seller has canceled the transaction, and the buyer has been refunded.
• Typical Use Case: Used when the seller decides not to proceed with the transaction (e.g., out-of-stock items, changed circumstances).

---

WAIT_FOR_ACCEPT

• Description: In a manual payment flow, the buyer’s account is debited, but the funds are on hold awaiting the seller’s acceptance.
• Typical Use Case: Common in marketplaces or platforms where the seller needs to confirm availability or service before finalizing the transaction.

---

FROZEN

• Description: The payment is blocked due to a dispute, investigation, or other issue requiring resolution. The buyer may be refunded, or the payment may be released once the issue is resolved.
• Typical Use Case: Used in fraud checks or dispute processes where funds must remain on hold until clarity on the transaction is reached.