Payments
Payments provide endpoints to filter both Charges and Payouts with multiple different parameters.
ModelsExpand Collapse
paymentSummaryPagedV1: object { data, meta, response_type }
data: array of object { id, amount, created_at, 17 more }
external_id: string
Unique identifier for the charge or payout in your database. This value must be unique across all charges or payouts.
payment_date: string
The desired date on which the payment should be occur. For charges, this means the date you want the customer to be debited on. For payouts, this means the date you want the funds to be sent from your bank account.
status_details: object { changed_at, message, reason, 2 more }
Details about the current status of the charge or payout.
customer_details: optional object { id, customer_type, email, 2 more }
Information about the customer associated with the charge or payout.
effective_at: optional string
The actual date on which the payment occurred. For charges, this is the date the customer was debited. For payouts, this is the date the funds were sent from your bank account.
funding_id: optional string
Unique identifier for the funding event associated with the charge or payout.
response_type: "object" or "array" or "error" or "none"
Indicates the structure of the returned content.
- "object" means the
datafield contains a single JSON object. - "array" means the
datafield contains an array of objects. - "error" means the
datafield contains an error object with details of the issue. - "none" means no data is returned.