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

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

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.

Test American Express Card Verification

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

1. 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.
2. 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.