Collect payments from customers’ bank accounts
paykey
- a token representing a verified bank account. Learn about connecting bank accounts in the Bridge guide.Field | Type | Description |
---|---|---|
id | string | Unique charge identifier |
paykey | string | Token for customer’s bank account |
amount | integer | Amount in cents (10000 = $100.00) |
currency | string | Currency code (USD only) |
description | string | Statement descriptor |
payment_date | string | Processing date (YYYY-MM-DD) |
status | string | Current payment status |
status_details | object | Detailed status information |
external_id | string | Your unique reference |
consent_type | string | How consent was obtained |
trace_number | string | ACH network tracking number |
funding_ids | array | Related settlement events |
10000
for $100.00"USD"
is supported."internet"
- Online or mobile app authorization"signed"
- Signed agreement or contract"telephone"
- Phone authorizationStatus | Description | Can Modify? |
---|---|---|
created | Initial state, awaiting verification | ✅ Yes |
scheduled | Verified and queued for processing | ✅ Yes |
pending | Sent to payment network | ❌ No |
paid | Successfully completed | ❌ No |
failed | Declined before funding | ❌ Terminal |
reversed | Returned after funding | ❌ Terminal |
cancelled | Stopped before network submission | ❌ Terminal |
on_hold | Paused for review | ⚠️ Depends |
pending
status, it has been submitted to the payment network and CANNOT be stopped, held, or cancelled.Field | Description |
---|---|
message | Human-readable explanation |
reason | Machine-readable reason code |
source | Where the status change originated |
code | ACH return code (when applicable) |
changed_at | When the status changed |
created
or scheduled
status:
pending
status:
created
or scheduled
status):
watchtower
source) cannot be released via API. They require manual review in the dashboard.Mode | Behavior | Use Case |
---|---|---|
enabled | Attempts check, proceeds if unavailable | Recommended - Best balance |
required | Must verify balance to proceed | High-value transactions |
disabled | No verification attempted | Future-dated charges |
required
will fail charges if:status_details
for specific information:
sandbox_outcome
in the config to simulate scenarios:
"paid"
- Successful charge"failed_insufficient_funds"
- NSF failure"on_hold_daily_limit"
- Risk hold"reversed_customer_dispute"
- Post-funding reversalexternal_id
to prevent duplicate charges