SHOWN ONCE
SANDBOX ONLYSave your secret
Store this secret in your test backend. It will disappear when you dismiss this panel or sign out.
INTEGRATION SANDBOX
Test the whole journey.
Create a link, simulate a payment, and follow it through to your backend.
GET STARTED
3 stepsFrom first request to verified event
- 1
Create an integration
Get a test API key for the sample approved plan.
- 2
Connect your webhook
Save its signing secret, verify your URL, then send a test event.
- 3
Make a test payment
Generate a link and choose an outcome on the sandbox checkout.
Production stays separate
Use a staging receiver and a test customer ledger. Sandbox notifications use the same event format as production, with their own integration IDs and signing secrets.
Recent payment links
CHECKOUT API
Payment links
Share a sandbox checkout and test what happens next.
Create a payment link
This form uses the same order validation as the sandbox API.
Test orders
Choose an outcome to exercise your integration’s recovery logic.
EVENT DELIVERY
Webhooks
Real signature verification. Simulated payment events.
Add a test receiving URL
Use your staging backend, separate from customer fulfillment in production.
Save → Verify → Test
Install the signing secret in your receiver first. Verification must return the signed challenge proof. An API success response only means verification is queued. Create new payment links after the endpoint becomes active to receive their events.
Receiving URLs
Delivery history
Retries keep the event ID. Your backend should fulfill each order only once.
SERVER TO SERVER
API integrations
Independent test credentials for your backend.
Create a sandbox integration
Each integration uses this workspace’s synthetic approved payment plan.
View the sandbox OpenAPI specification for payment links and webhook receiver contracts.
Your integrations
Make your first API request
Run this on your backend. Keep the API key out of browser and mobile code.
Set BIT_MARIO_TEST_KEY in your backend’s secret store. Persist the order ID and Idempotency-Key before sending. Production uses a different hostname and key.
How to confirm a payment
Use the authenticated status endpoint or a verified payment.completed webhook. Check the expected order, amount and currency. Polling and webhooks should call the same duplicate-safe fulfillment logic.