Card Refund Behavior

​

Practical guidance

• Initiate refunds only from your backend.
• Use your own refund request ID to prevent duplicate support actions.
• Wait for the resulting transaction status before updating final customer-facing state.
• Keep refund handling separate from chargeback handling.

​

Example request

{
  "amount": 2490,
  "reason": "requested_by_customer"
}

​

Example response

{
  "success": true,
  "requestId": "0190a2b4-18a7-7de0-9a43-69b7cf261201",
  "data": {
    "message": "Transaction refunded successfully",
    "amount_refunded": 2490,
    "remaining_balance": 0,
    "is_full_refund": true
  }
}

​

Integration rules

• A partial refund changes accounting state even if the order remains partially fulfilled.
• A full refund should close the customer-facing payment attempt.
• If the refund result is unclear, reconcile the transaction instead of retrying blindly.

​

Read next

• Transaction Statuses
• Payment Events