Get Started with Payments

To ensure that requests are processed correctly, you must test the basic success and error conditions for each service you plan to use.

Get Started with the REST API

Payment requests are submitted through the same REST API used for other merchant account operations — there is no separate SDK or endpoint base to install. You need a account with REST API authentication credentials before you can send authorization, capture, or credit requests. See Getting Started with the REST API for account creation, registration, and credential setup.

Requirements for Testing

Before you can test, contact customer support to activate the credit card services and configure your account for testing. You must also contact your processor to set up your processor account.

Contact your implementation team at customer support who can provide the test accounts.

Important

When building your connection to the payment gateway, ensure that you have implemented controls to prevent card testing or card enumeration attacks on your platform. For more information, see the best practices guide. When we detect suspicious transaction activity associated with your merchant ID, including a card testing or card enumeration attack, reserves the right to enable fraud management tools on your behalf to mitigate the attack. The fraud team might also implement internal controls to mitigate attack activity. These controls block traffic that is perceived as fraudulent. Additionally, if you are using one of our fraud tools and experience a significant attack, our internal team might modify or add rules to your configuration to help prevent the attack and minimize the threat to our infrastructure. However, any actions taken by would not replace the need for you to follow industry standard best practices to protect your systems, servers, and platforms.

Important

When building your connection to the payment gateway, ensure that you have implemented controls to prevent card testing or card enumeration attacks on your platform. When we detect suspicious transaction activity associated with your merchant ID, including a card testing or card enumeration attack, reserves the right to enable fraud management tools on your behalf to mitigate the attack. The fraud team might also implement internal controls to mitigate attack activity. These controls block traffic that is perceived as fraudulent. Additionally, if you are using one of our fraud tools and experience a significant attack, our internal team might modify or add rules to your configuration to help prevent the attack and minimize the threat to our infrastructure. However, any actions taken by would not replace the need for you to follow industry standard best practices to protect your systems, servers, and platforms.

Follow these requirements when you test your system:

Use your regular merchant ID (Org ID).
Use a real combination for the city, state, and postal code.
Use a real combination for the area code and telephone number.
Use a nonexistent account and domain name for the customer's email address.
REST API test endpoint: POST /pts/v2/payments

Use Test Card Numbers

Use these payment card numbers to test the authorization, capture, and credit services. Remove the spaces from the test card numbers when sending them to the test system. Do not use real payment card numbers. To test card types that are not included in the list, use an account number that is in the card's BIN range. For best results, try each test with a different service request and with different test payment card numbers.

American Express: 3782 8224 631X XX5
Discover: 6X11 1111 1111 1117
Maestro (International)
- 5X33 9619 89X9 17
- 5868 2416 0825 5333 38
Maestro (UK Domestic): the issue number is not required for Maestro (UK Domestic) transactions.
- 6759 4111 XXXX XXX8
- 6759 56XX 45XX 5727 054
- 5641 8211 1116 6669
Mastercard
- 2222 42XX XXXX 1113
- 2222 63XX XXXX 1125
- 5555 5555 5555 4444
Visa: 4111 1111 1111 1111

Jaywan: 669X 1XXX XXXX XXXX

JCB: 3566 1111 1111 1113

UATP (CVV not required)
- 1354 1234 5678 911
- 1485 1234 5678 9X5

eftpos Visa co-badged card
- 4434 X2XX XXXX XXX6
- 4X65 87XX XXXX XXXX
- 494X 53XX XXXX XXX1
eftpos Mastercard co-badged card
- 5163 6629 551X 5217
eftpos sole proprietary card
- 5X21 18XX XXXX XXX4
- 5X1X X7XX XXXX XXXX
- 5X18 X3XX XXXX XXX6

Test card numbers for testing 3-D Secure scenarios are available. For more information, go to the Payer Authentication Developer Guide.

China UnionPay Test Cards

Use these China UnionPay cards to test services. Replace each X with a 0 (zero) before using the card numbers.

Card Type	Details
Card-not-present 3-D Secure enabled card	Card: `625X947XXXXXXX14` · Expiration date (YYMM): `3312` · `CVV2`: `123`
Card-not-present 3-D Secure 2.2 enabled card	Frictionless: `81XXX1XXXXXXX142`, `621XX3823532713X` · Challenge: `81XXX1XXXXXXX688`, `621XX3257857442`
Domestic China-issued card	Card: `6222X4XXXXX3XX12` · Expiration date (YYMM): `4912` · CVV2: `123`
International-issued card	Card: `625X94X5XXXXXXX6` · Expiration date (YYMM): `4912` · CVV2: `123`
UnionPay International and Visa co-branded card	Card: `44278X2641XX4797` · Expiration date (YYMM): `4912` · CVV2: `123`
UnionPay International and Mastercard co-branded card	Card: `552XX123456789X3` · Expiration date (YYMM): `4912` · CVV2: `123`

Simulate Errors with Test Amounts

You can simulate error messages by requesting authorization, capture, or credit services with specific amounts that trigger the error messages. These triggers work only on the test server, not on the production server.

Each payment processor uses its own error messages.

For more information, see the REST API Testing Guide.

Test American Express Card Verification

Before using CVN with American Express, it is strongly recommended that you follow these steps:

Contact customer support to have your account configured for CVN. Until you do this, you will receive a 1 in the processorInformation.cardVerification.resultCode response field.
Test your system in production using a small currency amount, such as one currency unit. Instead of using the test account numbers, use a real payment card account number, and send an incorrect CVN in the request for authorization. The card should be refused and the request declined.

Next Steps

After completing your test transactions, proceed to the API reference to integrate payments into your application:

Authorizations — Submit authorization requests to verify payment credentials and reserve funds.
Captures — Capture previously authorized funds.
Sales — Perform a combined authorization and capture in a single request.
Endpoints — View all available payment endpoints and server URLs.

Was this page helpful?

Last published: September 29, 2026