Test the full flow — onboarding, payment, webhook, fulfillment — before you take real money.
Test mode
In test mode, no real funds move and you use test credentials. You can exercise every endpoint exactly as in production.
Test cards
Use standard processor test cards in the Payment Element:
| Card number | Behavior |
|---|---|
4242 4242 4242 4242 | Succeeds. |
4000 0000 0000 9995 | Declined (insufficient funds). |
4000 0025 0000 3155 | Requires 3-D Secure authentication. |
Use any future expiry, any CVC, and any postal code.
Testing ACH
ACH test payments move through processing → succeeded so you can verify your asynchronous
handling. Make sure you only fulfill on succeeded, never on processing.
Testing webhooks
Point your callback URL at a tunnel (or a test endpoint) and confirm you:
- Verify the
LC-Signatureheader. - Deduplicate on
LC-Event-Id. - Respond
2xxquickly.
Interactive console — coming soon
An in-docs Try it console (log in, use a sandbox key, and call endpoints right from these pages) is on the way. For now, test with cURL or your server code against test credentials. Ask us for early access.
Go-live checklist
- Onboarding reaches
enabledfor a real merchant. - A live payment reaches
succeededand your webhook fulfills the order. - Refunds and (if used) manual capture behave as expected.
- Your callback endpoint verifies signatures and is idempotent.