Wilby DocsGet Sandbox Keys

Bank Payments

ACH debits with the protections people expect from cards: a signed authorization, limits, approvals above them, and a record ready if a return is claimed.

1. The Customer Signs an ACH Debit Authorization

curl -X POST https://app.usewilby.com/v1/customers/ach-authorization-link \
  -H "Authorization: Bearer $OH_KEY" \
  -H "Idempotency-Key: bank-auth-1" \
  -H "content-type: application/json" \
  -d '{
       "customer_external_ref": "customer-1",
       "payment_method_ref": "pm_test_bank_ok",
       "per_order_cents": 10000,
       "range_cents": 1500,
       "days": 365
     }'

The customer signs on the page. range_cents is how much an order may change without asking again; above it, they approve the exact amount.

2. Orders Debit the Bank

Create, accept and fund an order as in the Quickstart, with the bank account as the payment method. The debit comes back pending and clears in a few days (POST /v1/sandbox/bank-reconcile clears test debits now).

3. Returns

Returned debits are recorded with their R-code. Retries follow Nacha's limits. GET /v1/bank-returns/health shows your return rates over 60 days against Nacha's thresholds (unauthorized 0.5%, administrative 3%, overall 15%), and webhooks warn you before you cross them.

Bank debits run on ACH. Instant rails (RTP, FedNow) are push-only, so they can't be debited.