Record a payment for one or more customer invoices. The payment is recorded and invoices are updated, ready to be matched during reconciliation later. Supports idempotency via Idempotency-Key header.
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.
Business UUID provided by Thred (unique identifier for the business)
Request serializer for recording invoice payments
UUID of the customer making the payment (must exist in business)
Total payment amount in cents (e.g., 450000 for £4,500.00)
x >= 1List of invoice allocations - how this payment should be applied to invoices
Date when payment was received (ISO date format: YYYY-MM-DD)
Payment currency (must match business base currency, e.g., GBP, EUR)
1 - 3Method of payment (e.g., bank_transfer, card, cash, cheque, direct_debit)
bank_transfer - bank_transfercredit_card - credit_carddebit_card - debit_cardach - achcheck - checkcash - cashpaypal - paypalstripe - stripeother - otherbank_transfer, credit_card, debit_card, ach, check, cash, paypal, stripe, other Your internal payment reference or receipt number
Your unique identifier for this payment (used for idempotency)
Internal note or description for the payment
Legacy field for notes (use 'note' instead)
Custom key-value pairs for additional payment context
Payment references (bank_reference, end_to_end_id, payment_reference)
Processing fee charged by payment processor (Stripe, PayPal, etc.) in cents
x >= 0Payment processor name (e.g., Stripe, PayPal)
100Response serializer for create invoice payment endpoint
Detailed payment information in response - all amounts in cents