- Introduction to Payments
- Standard Payment Processing
- Card Present Connect | Retail Processing
- Authorization with Contact EMV and Online PIN
- Authorization with Contact EMV and Offline PIN
- Card Present Connect | Mass Transit Processing
- American Express Delayed Online Authorization with EMV Data
- Tap-Initiated Authorization for Debt Recovery with EMV Data
- Debit and Prepaid Card Processing
- Processing Debit and Prepaid Authorizations
- Airline Data Processing
- Japanese Payment Options Processing
- Processing Payments Using Credentials
- Customer-Initiated Transactions with Credentials on File
- Delayed Transaction
- Incremental Transaction
- Merchant-Initiated Incremental Transaction with PAN
- No-Show Transactions
- Reauthorization Transaction
- Merchant-Initiated Reauthorization Transactions with PAN
- Resubmission Transaction
- Merchant-Initiated Resubmission Transaction with PAN
- Installment Payments
- Merchant-Initiated Installment Payments with PAN
- Recurring Payments
- Merchant-Initiated Recurring Payments with PAN
- Unscheduled COF Payments
- Token Management Service Processing
On This Page
Requirements for Testing
IMPORTANT
Before you can test, you must 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.
IMPORTANT
When building your connection to the
Cybersource
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. If we detect suspicious
transaction activity associated with your merchant ID, including a card testing or card
enumeration attack, Cybersource
reserves the right to enable fraud
management tools on your behalf in order to mitigate the attack. The fraud team might also
implement internal controls to mitigate attack activity. These controls will 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 Cybersource
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.
- 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:POSThttps://apitest.cybersource.com/pts/v2/payments