Charges
Charges represent attempts to debit money from a customer's bank account using a Paykey. Each charge includes automatic balance verification, real-time fraud screening, and multi-rail optimization and detailed status tracking throughout the payment lifecycle. Use charges to accept bank payments with confidence knowing every transaction is protected.
Lookup a charge
Update a charge
Create a charge
Hold a charge
Release a charge
Cancel a charge
Get a charge by id.
ModelsExpand Collapse
class ChargeV1:
required Data Data
required Config Config
required string ExternalID
Unique identifier for the charge in your database. This value must be unique across all charges.
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.
required IReadOnlyList<StatusHistory> StatusHistory
CustomerDetailsV1 CustomerDetails
DateTimeOffset? EffectiveAt
Timestamp of when the charge was effective in the customer's bank account, otherwise known as the date on which the customer is debited.
IReadOnlyDictionary<string, string>? Metadata
Up to 20 additional user-defined key-value pairs. Useful for storing additional information about the charge in a structured format.
PaykeyDetailsV1 PaykeyDetails
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.