DocsGuides

Going live

Check these before real traffic.

  1. Check you are on an `sb_live_` key and that X-Test-Scenario is gone. A live key returns 400 test_scenario_on_live_key if the header is still there. See Test mode.
  2. Store `livemode` with whatever you parsed for, so a fixture that reached your database can be found.
  3. Send an `Idempotency-Key` on every request, generated once per document and reused by every attempt. Without it, a timeout you retry is a second charge. See Idempotency and retries.
  4. Set a client timeout of at least 180 seconds. A long statement takes tens of seconds to parse, and a 30 second default turns a success into a retry.
  5. Filter on `account.type` before summing credits as income. See Amounts and directions.
  6. Branch on `verification.reconciled` and route anything false to a person. See Verification.
  7. Iterate `accounts` rather than reading accounts[0], and keep them separate. See Accounts and periods.
  8. Branch on `error.code`, not on the message or a substring of it.
  9. Keep four documents in flight or fewer, or handle 429 with a short backoff. See Limits.
  10. Store `doc.id` against whatever you parsed for. It is the handle for any support question later.

Volume#

Every organisation has a monthly document cap, which stops a runaway loop turning into an invoice. There is nothing to buy. Email [email protected] with your expected volume and we raise it before you hit it.

Support#

[email protected], with the documentId if there is one.

Something wrong or missing on this page? [email protected]