Create a payment for an existing refund. Supports idempotency via external_id.
Partner-level JWT token (unscoped). Token payload includes partner_id. Business access is validated via partner ownership. Format: Bearer <your-jwt-token>
Use this for: Multi-business operations where the business_id is specified in the URL and partner has access to multiple businesses.
Serializer for creating a refund payment (reusable for other endpoints). All amounts in cents.
Amount to disburse for this refund in cents (e.g., 20000 for €200.00)
x >= 1Payment method for the refund payment
CASH - CashCHECK - CheckCREDIT_CARD - Credit CardDEBIT_CARD - Debit CardACH - ACHBANK_TRANSFER - Bank TransferPAYPAL - PayPalSTRIPE - StripeOTHER - OtherCASH, CHECK, CREDIT_CARD, DEBIT_CARD, ACH, BANK_TRANSFER, PAYPAL, STRIPE, OTHER Required idempotency key per refund (unique within a refund)
1 - 255When the refund payment was completed
Payment processor
100Optional notes for the payment
Optional list of string tags for reconciliation
1 - 100Processing fee for this refund payment in cents (e.g., 30 for €0.30)
x >= 0Serializer for refund payments. All amounts in cents.
Unique refund payment identifier
ID of the refund this payment belongs to
Refunded amount in cents
Processing fee in cents
Bank transactions this refund payment is reconciled to
Timestamp when refund payment record was created
Timestamp when refund payment record was last updated
Your unique identifier for idempotency (unique within refund)
255Date and time when refund payment was completed
Payment method used for refund (CASH, CHECK, CREDIT_CARD, BANK_TRANSFER, etc.)
BANK_TRANSFER - Bank TransferCREDIT_CARD - Credit CardDEBIT_CARD - Debit CardACH - ACH/Direct DebitCHECK - Check/ChequeCASH - CashPAYPAL - PayPalSTRIPE - StripeOTHER - OtherBANK_TRANSFER, CREDIT_CARD, DEBIT_CARD, ACH, CHECK, CASH, PAYPAL, STRIPE, OTHER Payment processor used (e.g., Stripe, PayPal, manual)
100List of tags for categorization and reconciliation tracking
Optional description or notes for this refund payment
Custom key-value pairs for payment context