Connectivity - Developer Resources and Sandbox Environment
KA-07420
239
01/14/2026 17:31 PM
1.0
Introduction
This article provides an overview of Visa Acceptance Solutions developer resources, API documentation, sandbox testing tools, and important information about expected sandbox behavior. It also includes troubleshooting guidance for common 502-series errors and instructions on when to check the Status Page versus when to open a Support case.
To expedite troubleshooting of website, application, or API issues, please provide any associated reason codes, error codes, or request IDs when contacting Support.
Developer Center Resources
The Developer Centers provide documentation, sample code, and testing tools for integrating Cybersource and Visa Acceptance APIs.
API Developer Guides
API Reference
API Transaction Response Codes
Getting Started
Use the Hello World guides for first‑call setup and authentication.
Testing Guides and Sandbox Information
Testing Guides
Legacy API Sandbox Testing (Cybersource Only)
For Simple Order API, SOAP Toolkit, or SCMP testing information, visit:
Cybersource Testing Information
Sandbox Default Processor
Sandbox accounts default to Chase Paymentech. To configure a different processor, submit a Support case.
View Instructions
Sandbox Environment Behavior and Common Issues
The Sandbox environment is not optimized for performance and may experience intermittent instability. These behaviors do not impact Production environments.
Common Sandbox Issues
- Secure Acceptance test environments intermittently unavailable
- 502 or 504 timeout responses
- 150 / 151 system errors
- Missing or delayed transactions
- SOAP test endpoint unreachable
These issues often resolve on their own as Sandbox traffic varies globally throughout the day.
502-Series Errors: Meaning and Required Actions
The following table summarizes common 502 server errors across Payment, Capture, and Reversal services.
| Error | Meaning | Action | Retry? |
|---|---|---|---|
| 502 SYSTEM_ERROR | General system failure. | Review SDK retry guidance. | Yes, per SDK retry logic. |
| 502 SERVER_TIMEOUT | Request received but server timed out (not client-side timeout). | Check transaction status in Business Center before resending. | Do NOT retry until status is confirmed. |
| 502 SERVICE_TIMEOUT | Service received request but could not complete in time. | Check Business Center to confirm whether the transaction processed. | Do NOT retry until status is confirmed. |
| 502 INVALID_OR_MISSING_CONFIG | Invalid or missing merchant configuration. | Do not retry. Contact Support to correct configuration. | No – configuration must be fixed. |
Important: Sending retries without checking Business Center may cause duplicate transactions.
When to Check the Status Page vs. When to Open a Support Case
Check the Status Page First
If you experience Sandbox instability for more than 2 hours, or see widespread 502/504/timeout errors, review the Status Page:
Cybersource and Visa Acceptance Status Page
You may also sign up for notifications about new, ongoing, or resolved incidents.
When to Open a Support Case
Open a Support case if:
- The issue persists beyond 2 hours and the Status Page shows no active incidents.
- A configuration error is suspected (e.g., INVALID_OR_MISSING_CONFIG).
- Transactions fail consistently across multiple test attempts.
- SOAP or Secure Acceptance test endpoints remain unreachable.
Frontline Support will triage the issue and escalate to engineering when necessary.
GitHub Repositories
Access sample code and SDKs for .NET, Java, PHP, Ruby, and Python:
Cybersource GitHub Repository
Developer Center FAQs
Developer Center Support
If this article does not resolve your issue, contact us using the Developer Center support forms. Include any error codes, reason codes, or request IDs to speed resolution.
Additional Resources
Was this article helpful?