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.
Release a charge
Cancel a charge
Get a charge by id.
ModelsExpand Collapse
class ChargeV1: …
data: Data
config: DataConfig
Configuration options for the charge.
external_id: str
Unique identifier for the charge in your database. This value must be unique across all charges.
payment_date: date
The desired date on which the payment should be occur. For charges, this means the date you want the customer to be debited on.
Additional details about the current status of the charge.
status_history: List[DataStatusHistory]
Status history.
reason: Literal["insufficient_funds", "closed_bank_account", "invalid_bank_account", 24 more]
A machine-readable identifier for the specific status, useful for programmatic handling.
customer_details: Optional[CustomerDetailsV1]
Information about the customer associated with the charge.
effective_at: Optional[datetime]
Timestamp of when the charge was effective in the customer's bank account, otherwise known as the date on which the customer is debited.
metadata: Optional[Dict[str, str]]
Up to 20 additional user-defined key-value pairs. Useful for storing additional information about the charge in a structured format.
paykey_details: Optional[PaykeyDetailsV1]
response_type: Literal["object", "array", "error", "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.
class ChargeUnmaskResponse: …
data: Data
config: DataConfig
status_history: List[DataStatusHistory]
Status history.
reason: Literal["insufficient_funds", "closed_bank_account", "invalid_bank_account", 24 more]
A machine-readable identifier for the specific status, useful for programmatic handling.
customer_details: Optional[CustomerDetailsV1]
Information about the customer associated with the charge or payout.
response_type: Literal["object", "array", "error", "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.