Testing

To confirm that your integration works correctly, simulate transactions without moving any money using special values in Test environment.

Retrieve your Test API Keys from your Account.

Test payment methods let you simulate several scenarios:

• Succeeded payments by card brand
• Card errors due to declines, fraud, or invalid data
• Refunds
• Payouts

When you're ready to take your integration live, replace your Test publishable and secret API keys with Production ones. You can't process live payments if your integration is still using your test API keys.

Test environment

Each account has a Test and a Production environment. See Accounts. Test mode uses the same API host as production, and your Test API keys select the test environment. Card collection and card details sent with a payment have their own test hostnames:

Use	Host	Key
API requests	https://api.publicsquare.com	Test Secret Key
Save a card	https://collect-test.publicsquare.com	Test Publishable Key
Send card details with a payment or payout	https://secure.payments.sbx.credova.com	Test Secret Key

Elements SDK version 1.16.1 and later work with test keys against a production account. See the SDK versions.

Cards

The following card numbers can be used for testing your integration while in Test environment.

Cards by brand

Brand	Number	CVC	Expiration Date
Visa	4242424242424242	Any 3 digits	Any future date
Mastercard	5555555555554444	Any 3 digits	Any future date
American Express	378282246310005	Any 4 digits	Any future date
Discover	6011111111111117	Any 3 digits	Any future date
Diners Club	3056930009020004	Any 3 digits	Any future date
UnionPay	6200000000000005	Any 3 digits	Any future date

Declined payments

Decline Reason	Number	Payment Status
Decline	4000000000000002	declined
Insufficient Funds	4000000000009995	declined
Lost/Stolen	4000000000009987	declined

Declined payouts

Decline Reason	Number	Payment Status
Decline	4000000000000002	declined
Lost/Stolen	4000000000009987	declined

Declined payments during capture

Decline Reason	Number	Payment Status
Settlement amount is not equal to authorized amount	4000000000000119	declined

Fraudulent payments

Description	Number	Payment Status	Fraud Decision	AVS Code	CVV2 Reply
Rejected fraud decision	4100000000000019	rejected	reject	Y	M
Review fraud decision	4000000000009235	succeeded	review	Y	M
CVC check fails	4000000000000101	rejected	reject	Y	N
Postal code check fails	4000000000000036	succeeded	review	A	M
Address Line1 check fails	4000000000000028	succeeded	review	Z	M
Address check fails	4000000000000010	rejected	reject	N	M

3D Secure

3DS authentication is triggered by the card number. Use any future expiration date, any CVV and any billing ZIP. See 3D Secure for how authentication works.

Scenario	Card number	Brand	Expected result
Frictionless success	5204247750001471	Mastercard	succeeded, no challenge
Frictionless success	340000000004001	Amex	succeeded, no challenge
Challenge success	4000020000000000	Visa	challenge → succeeded
Challenge success	370000000000002	Amex	challenge → succeeded
Mandated challenge	4761369980320253	Visa	challenge → succeeded
Mandated challenge	5200000000001104	Mastercard	challenge → succeeded
Out-of-band challenge	4000000000000341	Visa	challenge → succeeded
Authentication attempted	4111111111111111	Visa	succeeded (partial shift)
Authentication attempted	5424180011113336	Mastercard	succeeded (partial shift)
Authentication failed	4264281511112228	Visa	failed
Authentication failed	5424180000000171	Mastercard	failed
Authentication unavailable	5405001111111165	Mastercard	failed
Authentication rejected	5405001111111116	Mastercard	failed
Failed challenge	4055011111111111	Visa	challenge → failed
Failed challenge	5427660064241339	Mastercard	challenge → failed
Directory server error	4264281500003339	Visa	failed (error surfaced)
Internal server error	4264281500001119	Visa	failed (error surfaced)

Bank accounts

The following bank accounts can be used for testing your integration while in Test environment. The payment/payment status will initially be pending. For payments, after a short period of time, the payment status will be updated and a payment:update Webhook will be sent with the payment in the entity of the payload. For payouts, the payout status will be updated and a payout:update Webhook will be sent with the payout in the entity of the payload.

Routing	Number	Payment Status	Decline Reason
110000000	000123456789	succeeded	N/A
110000000	000111111113	declined	Account Closed
110000000	000111111116	declined	Invalid Account Number
110000000	000222222227	declined	Insufficient Funds
110000000	000555555559	declined	Decline. Customer cancellation
110000000	000333333335	declined	Stop Payment Order
110000000	000444444440	declined	Account Locked

Transaction amounts

You can use specific payment amounts to trigger different responses during processing. The test payment methods will be evaluated first before checking the payment amount:

Amount($)	Authorize/Sale	Capture	Fraud Decision
2000	rejected	N/A	accept
3000	succeeded	N/A	review
4000	error	N/A	accept
5000	declined	N/A	accept
6000	requires_capture	declined	accept

Dispute cases

You can use specific card payment amounts to trigger the generation of dispute cases to simulate chargebacks and inquiries from the credit card networks. The test amount will be evaluated only for card payments, and generate a dispute with the defined status. Adjustments to simulate the flow of back-and-forth of funds during a chargeback process will also be created:

Amount($)	Status	Evidence Submitted	# of Adjustments
7000	needs_response	false	1
7100	under_review	true	2
7200	won	true	2
7300	lost	true	3
7400	warning_needs_response	false	0
7500	warning_under_review	true	0
7600	warning_close	true	0