Use 12 Stripe-documented US bank account examples to test ACH success and failure paths in Stripe test mode. These values are provider fixtures, not randomly generated bank accounts or live payment credentials.
Inspect the first fixture and provider catalog metadata before authenticating.
Explore preview a provider →Paid API access can export the provider matrix as JSON or CSV under plan limits.
Explore export for ci →Assert provider state transitions and webhook handling in a deterministic local test.
Explore connect the outcome →Use these values only in the provider's test environment. They are not account verification, live credentials or generic random bank-account output.
| Scenario | Routing number | Account number | Expected outcome |
|---|---|---|---|
| payment succeeds | 110000000 |
000123456789 |
succeeded |
| account closed | 110000000 |
000111111113 |
requires payment method |
Verify all values in the provider's documentation. Open the full fixture workflow for source-linked exports.
Open the documented source or runtime contract before relying on this workflow.
View source →Page evidence checked 2026-09-23No. They are synthetic or provider-sandbox examples for QA and contract testing. Never submit them to a live payment flow.
Depending on the provider, rows can include scenario, sandbox routing/account number or IBAN, token, expected status, webhook and source context.
Yes. Use the Business intake to submit a bounded provider and scenario list; coverage is reviewed before any implementation or commercial promise.