Merchant setup
Set up staging first, then production.
Alpha normally provisions a staging account first so your team can test the full payment lifecycle before live credentials, production KYB, and production money movement are enabled.
What Alpha gives you
- A staging merchant account and invite link for your first owner user.
- Access to staging portal, staging API, and staging checkout hosts.
- Permission to create staging test API keys and webhook endpoints.
- Access to Test Shop and Test Center for checkout, webhook, refund, settlement, chargeback, and payout rehearsal.
- A production merchant account after onboarding approval, with separate production keys and webhooks.
Merchant responsibilities before integration
- Use staging and test data only in staging. Do not use real customer payment details, production customer PII, or live beneficiary credentials in sandbox tools.
- Enable 2FA before creating production keys, webhooks, payout methods, or live operational workflows.
- Keep API keys server-side. Do not put secret keys in browser code, mobile apps, screenshots, tickets, or chat.
- Host a public HTTPS webhook receiver and verify Alpha signatures before accepting events.
- Make payment creation idempotent from your server using a stable order or payment attempt key.
- Decide how your shop handles pending, completed, failed, cancelled, expired, refunded, and disputed states.
Enable two-factor authentication
2FA protects account sign-in and sensitive actions such as API key changes, webhook changes, refunds, funding, and payouts.
- Open Settings in the merchant dashboard.
- Choose an authenticator app or email one-time code.
- Confirm setup with the current code.
- Save backup codes in a password manager or approved secret store.
Environment separation
| Environment | Portal | API | Checkout | Use |
|---|---|---|---|---|
| Test | https://test.alphadigiwallet.com | https://test-api.alphadigiwallet.com | https://checkout-test.alphadigiwallet.com | Shared sandbox and automated E2E target. |
| Staging | https://staging.alphadigiwallet.com | https://staging-api.alphadigiwallet.com | https://checkout-staging.alphadigiwallet.com | Merchant pilot and integration rehearsal. |
| Production | https://app.alphadigiwallet.com | https://api.alphadigiwallet.com | https://checkout.alphadigiwallet.com | Live merchant operations after approval. |
Important
Keys, webhooks, data, routes, and checkout URLs are environment-specific. Never reuse staging webhook secrets or staging API keys in production.Production account and KYB
Production access is separate from staging. Upload KYB documents in the production portal when Alpha asks for them. Production approval, pricing, reserve policy, settlement timing, payout readiness, and support contacts must be confirmed before live traffic.
Common KYB documents
- Certificate of incorporation or business registration.
- Director/controller identification where required.
- Proof of business address.
- Bank or payout account evidence where applicable.
- Website/product and prohibited-business review information.
Go-live controls
- Production KYB approved.
- Live keys created and stored server-side.
- Production webhook endpoints registered and monitored.
- Pricing, reserves, settlement currency, and payout schedule confirmed.
- One low-value live transaction completed before full cutover.
Next step
After staging access is ready, build the server-side payment creation flow and webhook receiver.
1. Create a staging secret key in /merchant/developers
2. Create a staging webhook endpoint in /merchant/webhooks
3. Build POST /v1/payments from your server
4. Redirect the buyer to checkout_url
5. Fulfil orders from webhook-confirmed payment.completed events