Sandbox
Test every flow on Stage. Move no real money.
Stage mirrors production: the same API contract, the same webhooks and its own Business Portal. You build and test against the contract you will run live. Only the money is simulated.
- Mirrors production
- Test cards and simulators
- Postman collection
Mirrors productionOverview
USD
1,284,560.00
+4.2%
BRL
3,420,118.40
+12.8%
MXN
8,905,332.10
+6.1%
- Pay-in · Pixorder_8F2K-1043+ R$ 1,250.00
- Payout · SPEIseller_0921− MX$ 18,400.00
- FX · BRL → USDfx_3b7q250,000.00 USD
- Pay-in · Bre-Border_9A1C-2210+ COP 890,000
Environments
Two environments, one integration
Switch environments by changing the base URL and the credentials you load.
API base URL
- Stage (sandbox)
- https://api.stage.localpayment.com
- Production
- https://api.v3.localpayment.com
Business Portal
- Stage (sandbox)
- ui.stage.localpayment.com
- Production
- ui.v3.localpayment.com
Money
- Stage (sandbox)
- Simulated: no real funds move
- Production
- Real funds over real rails
Credentials
- Stage (sandbox)
- Issued when the partnership starts
- Production
- Issued after Stage testing, security review and KYB
Data
- Stage (sandbox)
- Fictitious test data only
- Production
- Real customer data, protected by your controls and ours
IP allow-listing
- Stage (sandbox)
- Required
- Production
- Required
Stage and Production credentials are different. Store them as separate secrets.
What you can test
Rehearse what you will run in production
Card pay-ins
Approvals, declines, 3D Secure challenges and processing errors, each with its own test card number.
Virtual accounts
Create accounts and simulate incoming transfers to exercise matching, reconciliation and webhooks.
Local payment methods
Create Pix and other local-method pay-ins and inspect QR codes, payment instructions and pending statuses.
Payouts
Run the documented payout sandbox scenarios to see each status along the payout flow.
Webhooks end to end
Point a Stage notification URL at your endpoint and verify signatures before production.
Failure handling
Replay an externalId to see 409 Conflict, let a token expire and practice retries with backoff.
Test cards
Card numbers for every outcome
Use any future expiry date. CVC: any 3 digits (4 for Amex).
4242 4242 4242 4242
- Result
- Approved
- Use it to test
- The happy path: authorization, confirmation and webhook
4000 0000 0000 0002
- Result
- Declined
- Use it to test
- Decline messages and retry prompts in your checkout
4000 0025 0000 3155
- Result
- 3D Secure challenge
- Use it to test
- The authentication step and the return to your flow
4000 0000 0000 9995
- Result
- Processing error
- Use it to test
- Error handling, logging and customer messaging
For Stage only. Card acceptance is available in Argentina, Colombia, Mexico and Peru; 3D Secure applies in Colombia, Mexico and Peru.
Virtual account simulator
Simulate a bank transfer on demand
No need to wait for a real transfer: create a virtual account on Stage, call the simulator and follow the simulated payment through matching, status updates and your notification handling.
- POST /api/simulate/va is available on Stage only
- Use it to exercise your VirtualAccount webhook handling before go-live
- Ideal for automated end-to-end tests in your CI pipeline
# Stage only. Illustrative bodies: see the testing guide for the exact contract.
# 1) Create a virtual account for a test customer (Mexico, CLABE)
curl -X POST https://api.stage.localpayment.com/api/virtual-account \
-H "Authorization: Bearer $ACCESS_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"externalId": "3b9f6c1e-0000-4000-8000-000000000123",
"country": "MEX",
"currency": "MXN",
"beneficiary": { "name": "Ana Torres", "document": { "type": "RFC", "id": "TOAA800101XXX" } }
}'
# 2) Simulate an incoming bank transfer to that account
curl -X POST https://api.stage.localpayment.com/api/simulate/va \
-H "Authorization: Bearer $ACCESS_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"accountNumber": "646180000000004821",
"amount": 1250.00,
"currency": "MXN"
}'
# 3) Your webhook endpoint receives a VirtualAccount notificationPostman
Import the collection, send your first request
The Localpayment Postman collection ships with a Stage environment file, so you can explore the API before writing a line of code.
- A STAGE environment file that points every request at the sandbox
- Use it alongside the API reference to inspect request and response shapes
- Add your Stage credentials locally, and never share a workspace that contains them
Good practice
Test like it is production
Fictitious data only
Use made-up names and document numbers. Never load real customer or card data into Stage.
Separate secrets
Keep Stage and Production credentials apart, each in your secrets manager.
Test the unhappy paths
Declines, 3D Secure, timeouts, 409 duplicates and expired tokens, not just approvals.
Exercise webhook retries
Return a non-200 once and confirm your handler applies the retried delivery exactly once.
Respect token lifetimes
Access tokens last 5 minutes. Build refresh logic now, not after go-live.
Automate your suite
Run end-to-end tests against Stage in CI, using the virtual account simulator.
Getting access
How to get Stage credentials
- 01
Tell us about your project
Share your use case, markets and expected volumes through the contact form.
- 02
Start the partnership
Commercial terms are agreed and onboarding begins, including a compliance review.
- 03
Receive Stage credentials
You get an API user and password for Stage, plus access to the Stage Business Portal.
- 04
Allow-list and build
Add your server IPs, import the Postman collection and follow the quickstart.
Sandbox FAQ
Does Stage move real money?
No. Stage mirrors production behavior with simulated funds. Nothing you do there reaches a real bank, card network or wallet.
Can I use real customer data on Stage?
No. Use fictitious names, document numbers and cards only. Real personal or card data must never be sent to a test environment.
How does Stage differ from Production?
The API contract and webhooks are the same. Payments are simulated (virtual account transfers, for example, come from the simulator), so timings do not reflect real rails.
How do I move to Production?
Complete Stage testing, the security review and business verification (KYB). We then issue production credentials. The quickstart includes the full go-live checklist.
Who do I contact if something does not work?
Email support@localpayment.com, available 24/7, or use “Ask AI” in the docs for quick answers.
Get your Stage credentials
Start the conversation with our team. Stage access is issued when your partnership begins.