Payments
Payments provide endpoints to filter both Charges and Payouts with multiple different parameters.
Search payments
PaymentSummaryPagedV1 Payments.List(PaymentListParams?parameters, CancellationTokencancellationToken = default)
GET/v1/payments
ModelsExpand Collapse
class PaymentSummaryPagedV1:
class PaymentSummaryPagedV1:
required IReadOnlyList<Data> Data
required IReadOnlyList<Data> Data
required string ExternalID
required string ExternalID
Unique identifier for the charge or payout in your database. This value must be unique across all charges or payouts.
required DateOnly PaymentDate
required DateOnly PaymentDate
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.
formatdate
CustomerDetailsV1 CustomerDetails
CustomerDetailsV1 CustomerDetails
DateTimeOffset? EffectiveAt
DateTimeOffset? EffectiveAt
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.
formatdate-time
string? FundingID
string? FundingID
Unique identifier for the funding event associated with the charge or payout.
formatuuid
PaykeyDetailsV1 PaykeyDetails
PaykeyDetailsV1 PaykeyDetails
required Meta Meta
required Meta Meta
required ResponseType ResponseType
required ResponseType ResponseType
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.