Testing Scenarios Guide
The Aurora Payments Sandbox environment is a fully isolated sandbox that mirrors production behavior without processing real transactions. Use it to validate your integration before going live.
This guide covers everything you need to test your integration thoroughly — from basic happy-path flows to edge cases, automated test suites, and load testing.
All examples in this guide use the Sandbox base URL: https://uat.arise.risewithaurora.com
Test Environment Setup
Prerequisites
Before running tests, ensure you have:
- A Sandbox merchant account provisioned by Aurora.
- A Sandbox API Key (Client ID and Client Secret). See Creating an API Key.
- An API Token generated from your Sandbox credentials. See Creating an API Token.
Test Card Numbers and Scenarios
Use the following card numbers in the Sandbox environment to simulate specific payment outcomes. These cards are only valid in Sandbox and will be rejected in production.
Successful Transactions
| Card Number | Brand | CVV | Expiry |
|---|---|---|---|
| 4012 0000 9876 5439 | Visa | 999 | Any future date |
| 4111 1111 1111 1111 | Visa | 999 | Any future date |
| 5146 3150 0000 0055 | Mastercard | 998 | Any future date |
| 5146 3122 0000 0035 | Mastercard | 998 | Any future date |
| 5282 2651 9026 0890 | Mastercard | 998 | Any future date |
| 3714 496353 92376 | Amex | 9997 | Any future date |
| 3770 270560 60401 | Amex | 9997 | Any future date |
| 3702 951011 14559 | Amex | 9997 | Any future date |
| 6011 0009 9302 6909 | Discover | 996 | Any future date |
| 6011 9601 1794 1160 | Discover | 996 | Any future date |
Declined Transactions
| Card Number | Transaction Amount | Scenario | Expected Error Code |
|---|---|---|---|
| Any Testing Card with wrong CVV | Any amount | Declined (Wrong CVV) | N7 CVV2 verification failed |
| Any Visa Card | $0.06 | Declined (Pick up card) | 07 Pick up card, special condition (fraud account) |
| Any Visa Card | $0.07 | Declined (Lost Card) | 41 Lost card, pick up (fraud account) |
| Any Visa Card | $0.08 | Declined (Stolen Card) | 43 Stolen card, pick up (fraud account) |
| Any Visa Card | $0.21 | Declined (Insufficient funds) | 51 Insufficient funds |
| Any Visa Card | $0.23 | Declined (Withdrawal Limit exceeded) | 61 Exceeds approval amount limit |
| Any Visa Card | $51.00 | Declined (Partial decline) | Partial authorization (sale) is not allowed, decline. |
| Any Visa Card | $0.45 | Failed Transaction | 96 SYSTEM ERROR |
Address Verification Service (AVS) Scenarios
| Address Field | Expected Value for AVS Pass |
|---|---|
| Address (Line 1) | 8320 |
| Zip Code | 85284 |
Test ACH Account Numbers and Scenarios
Use the following account numbers in the Sandbox environment to simulate specific payment outcomes. These accounts are only valid in Sandbox and will be rejected in production.
Successful Transactions
| Routing Number | Account Number | Account Type | Scenario |
|---|---|---|---|
| 021000021 | Any Number (9-12 chars) | Any | Successful ACH transaction |
| 011401533 | Any Number (9-12 chars) | Any | Successful ACH transaction |
| 091000019 | Any Number (9-12 chars) | Any | Successful ACH transaction |
Declined ACH Transactions
| Routing Number | Account Number | Account Type | Scenario |
|---|---|---|---|
| 123123123 | 111111111 | Any | Returned NSF (next day) |
| 123123123 | 222222222 | Any | Returned Other (next day) |
| 123123123 | 444444444 | Any | Cleared, then Charged Back (next day) |
| 123123123 | 987654321 | Any | Fails Express Verify (immediate) |
| 123123123 | 999999999 | Any | Fails Verify Plus |
Error Condition Testing
Test each error type to ensure your integration handles failures gracefully and communicates clearly with end users.
HTTP Error Codes
| HTTP Status | Error Code | Common Cause | Handling Recommendation |
|---|---|---|---|
| 400 | VALIDATION_ERROR | Missing or malformed request field | Display field-level validation messages to the user |
| 401 | UNAUTHORIZED | Missing, expired, or invalid token | Refresh the token and retry the request once |
| 403 | FORBIDDEN | Token lacks required permission | Check API Key permissions in the merchant portal |
| 404 | NOT_FOUND | Resource does not exist or belongs to another merchant | Verify the resource ID and merchant scope |
| 429 | RATE_LIMITED | Too many requests in a short period | Implement exponential backoff with jitter |
| 500 | INTERNAL_ERROR | Unexpected server error | Retry with exponential backoff; alert if persistent |
| 503 | SERVICE_UNAVAILABLE | Aurora service temporarily unavailable | Retry after a delay; do not retry immediately |
Edge Case Handling
Duplicate Transactions
Submit two identical requests with the same Reference ID value within a short window (Default: 10 minutes).
TBD
Load Testing
Coordinate with Aurora before running load tests against the Sandbox environment. High traffic against shared Sandbox infrastructure can affect other merchants using the same environment. Contact isvsupport@risewithaurora.com to schedule a load test window.
What to Measure
Focus your load tests on the endpoints your integration uses most heavily. For each endpoint, measure:
| Metric | Acceptable Target | Notes |
|---|---|---|
| P95 latency | < 2 seconds | For token creation and payment session endpoints |
| P99 latency | < 5 seconds | Under sustained load |
| Error rate | < 0.1% | Excluding intentional decline scenarios |
| Throughput | Match expected peak TPS | Ramp up gradually — do not start at peak |
| Token refresh success rate | 100% | Tokens must never silently fail to refresh |