Using debit-card test data in a checkout flow
Generate debit-card sandbox fixtures, preserve the funding label in tests, and check your checkout without using real banking details.
Keep debit fixtures separate
A payment interface may need to show or handle a provider’s funding classification. A debit-card fixture lets you exercise that branch intentionally, instead of assuming that every Visa or Mastercard record represents the same funding type.
The default debit generator produces unique synthetic records with funding set to debit. It does not infer a live issuer or account. Sandbox mode uses documented funding labels where the provider supplies them; otherwise the field says unspecified.
Create a small, labeled dataset
Choose a brand and generate one to 50 records, with optional billing addresses. Each has a unique number, name, expiry pair and CVV. Seven brand formats include 15-digit American Express and 14-digit Diners Club.
Copy a field from its preview or export JSON and CSV. For processor integration tests, switch to Payment sandbox numbers and select the provider. Sandbox batch size cannot exceed the documented distinct numbers for that selection.
curl https://kivel.io/api/tools/developer-debit-card-generator/run \
-H 'Content-Type: application/json' \
-d '{"options":{"brand":"mastercard","count":"1"}}'Assert the behavior you own
Check that a debit result is displayed with the right funding label, that the saved-payment summary remains readable, and that the form preserves the entered values when a request fails.
Use the provider’s test environment for payment behavior. Your local UI fixtures can test rendering and branching, but they do not prove how a particular bank, account, or live transaction will behave. A checksum check cannot establish that either.
Use the same data from a script
The generator is available through the shared Kivel execution endpoint. SDK, CLI, SSH, and MCP clients use the same tool ID and string options. Browser generation is local; hosted calls count toward the normal daily allowance.
Store these records as clearly named test fixtures. Generated records and documented sandbox values contain no customer banking details and must never be used for live payments.