Alpha DigiWallet

Merchant functionality

Everything a merchant can use in Alpha DigiWallet.

A practical map of portal pages, integration APIs, hosted checkout, webhooks, payouts, settlements, chargebacks, support, and the non-production Test Shop and Test Center.

Test Shop and Test CenterMerchant onboarding checklistOpenAPI JSON
Portal
16 merchant routes
Security
2FA protected actions
Sandbox
Test Shop + Test Center
Where to work

Use the right environment for the job.

Each environment has its own portal, API host, checkout host, keys, webhook secrets, and data.

Portal

Merchant dashboard capabilities.

These are the active merchant-facing pages in the Go-backed product portal.

Account and Security

Registration, email verification, login, password reset, TOTP or email OTP, and step-up for sensitive actions.

/login/register/verify-email

Profile and KYB

Business profile updates, KYB document upload, document status, and reviewer feedback where available.

/merchant/profile/merchant/verification

Team Management

Owner/admin controls for invitations, roles, deactivation, and pending invite revocation.

/merchant/team/accept-invite/token

API Keys

Create test or live publishable and secret keys, copy secrets once, and revoke old keys with step-up.

/merchant/developers

Payments

Create hosted checkout payments, browse payment history, inspect payment detail, and issue refunds.

/merchant/payments/merchant/transactions

Webhooks

Register signed HTTPS endpoints, choose event subscriptions, inspect delivery logs, and retry failures.

/merchant/webhooks

Funding

Create hosted-checkout merchant top-ups and track top-up status separately from buyer payments.

/merchant/funding

Payouts

Open account currencies, manage payout methods, quote source debits and fees, and initiate payouts.

/merchant/payouts/merchant/payouts/methods/merchant/payouts/new

Settlements

Review Alpha settlement batches, gross/fee/reserve/net amounts, transaction counts, and FX summaries.

/merchant/settlements

Chargebacks

Track disputes, evidence deadlines, chargeback fees, outcomes, and supporting evidence records.

/merchant/chargebacks

Analytics

Review volume, refunds, chargebacks, success rate, status mix, currency mix, and top customer spend.

/merchant/analytics

Support

Open support tickets, see ticket status, and continue chat-style support conversations.

/merchant/support
Integration

API, checkout, and webhook surfaces.

Merchants create payments from their server, redirect buyers to hosted checkout, and reconcile outcomes with Alpha ids and statuses.

1. Create API keys

Generate a test secret key in the merchant portal. Secret plaintext is shown only once.

2. Create hosted checkout payments

Call POST /v1/payments from your server, then send the buyer to the returned checkout URL.

3. Register signed webhooks

Subscribe to payment, merchant top-up, payout, settlement, and chargeback events.

4. Reconcile status

Use webhooks, payment reads, settlement records, and ledger balances to reconcile operations.

Merchant API map

AreaMethodPathUse
API keysGET/POST/DELETE/v1/api-keysDashboard key lifecycle with step-up on create and revoke.
PaymentsPOST/GET/v1/paymentsServer-side payment creation and API-key payment reads.
Dashboard paymentsGET/POST/v1/merchant-paymentsSession-scoped payment browsing and refunds.
Top-upsPOST/GET/v1/merchant-topupsMerchant funding checkouts and status reads.
WebhooksGET/POST/DELETE/v1/webhook-endpointsEndpoint setup, delivery logs, and retries.
PayoutsGET/POST/v1/payoutsPayout history, quotes, initiation, and cancellation where eligible.
LedgerGET/v1/merchant-ledger/*Balances and ledger entries by currency.
SettlementsGET/v1/settlementsMerchant settlement batch visibility.
ChargebacksGET/POST/v1/chargebacksDispute list/detail and evidence records.
SupportGET/POST/v1/support/ticketsTicket creation and replies.

Create a staging payment

curl -X POST https://staging-api.alphadigiwallet.com/v1/payments \
  -H "Authorization: Bearer sk_test_..." \
  -H "Idempotency-Key: order-a1001" \
  -H "Content-Type: application/json" \
  -d '{
    "amount": "25.00",
    "currency": "USD",
    "customer_email": "buyer@example.com",
    "success_url": "https://merchant.example/success",
    "cancel_url": "https://merchant.example/cancel",
    "description": "Order A1001"
  }'

Refund from merchant session

curl -X POST https://staging-api.alphadigiwallet.com/v1/merchant-payments/{payment_id}/refund \
  -H "Authorization: Bearer <merchant_session_token>" \
  -H "X-Step-Up-Token: <step_up_token>" \
  -H "Idempotency-Key: refund-a1001" \
  -H "Content-Type: application/json" \
  -d '{"amount":"10.00","reason":"customer_request"}'
Events

Webhook events merchants can subscribe to.

Webhook endpoints are created from the merchant dashboard. Alpha signs each outbound delivery and lets merchants retry failed deliveries.

Delivery controls

  • Create/delete endpoints with step-up.
  • Store signing secrets at creation.
  • Inspect delivery status and retry failed deliveries.
payment.createdpayment.completedpayment.failedpayment.cancelledpayment.refundedpayment.refund_failedrefund.createdrefund.processingrefund.completedrefund.failedmerchant_topup.completedmerchant_topup.failedmerchant_topup.cancelledpayout.createdpayout.requestedpayout.approvedpayout.processingpayout.completedpayout.failedpayout.cancelledpayout.returneddispute.createddispute.evidence_requireddispute.updateddispute.wondispute.lostchargeback.createdchargeback.evidence_requiredchargeback.wonchargeback.lostsettlement.createdsettlement.reconciledsettlement.exception_createdwebhook.test
Operations

Funding, payouts, settlements, and disputes.

Completed payments are not payoutable until settlement or funding reconciliation credits the merchant ledger.

Funding

  • Hosted-checkout top-ups
  • merchant_topup webhooks
  • Separate from buyer payments

Payouts

  • Payout methods
  • Quote before initiation
  • Source balance and fee freeze

Settlements

  • Gross, fees, reserve, net
  • Transaction count
  • Optional FX summaries

Chargebacks

  • Evidence deadlines
  • Evidence records
  • Won/lost/received outcomes
Sandbox

Use Test Shop and Test Center before live traffic.

Both tools are intentionally absent from production. Use only test or staging API keys, test payment details, and non-production beneficiary details.

Browser Test Shop

Checkout rehearsal for non-developer users.

  1. 1Log in to staging or test as a merchant.
  2. 2Open the browser Test Shop from the portal or direct URL.
  3. 3Create the built-in webhook capture endpoint.
  4. 4Paste a non-production sk_test secret key.
  5. 5Create a checkout and open the hosted checkout URL.
  6. 6Refresh payment and webhook status until the event arrives.
  7. 7After completion, initiate a merchant-session refund from the page.
Open staging Test Shop Open test Test Shop

Merchant Test Center

Self-service simulator controls for owner/admin users.

  • Send sample webhook events to subscribed endpoints.
  • Create received, won, or lost chargebacks on completed test payments.
  • Generate sample settlement and reconciliation outcomes for completed test payments.
  • Move staging payout requests through sample outcomes without Alpha support.
  • Jump directly to payments, webhooks, settlements, chargebacks, payouts, and Test Shop.
Open staging Test Center Open test Test Center
Production keys, real customer payment details, production customer PII, and live beneficiary credentials must not be used in Test Shop or Test Center.
Checklists

Staging and production onboarding checklists.

Run staging first, then cut over with separate production keys and webhooks.

Staging checklist

Before you start

  1. Complete invite-based onboarding, email verification, and 2FA.
  2. Submit KYB documents for review.
  3. Confirm staging account status and test-mode settings are correct.

API keys and webhooks

  1. Create a staging secret key in `/merchant/developers`.
  2. Use staging scope-specific keys (minimum scopes for required APIs).
  3. Save the key once; never share it in plain text.
  4. Create staging HTTPS webhook endpoints and copy signing secrets once.

Functional checks

  1. Create test payments from API and follow checkout redirect flow.
  2. Verify webhook delivery and retry behavior in the webhooks dashboard.
  3. Run refund flows on completed test payments.
  4. Use `/merchant/test-center` for sandbox chargebacks and settlement import.
  5. Create test funding top-ups and verify merchant_topup webhooks.
  6. Run payout method add/quote/initiate dry-runs.

Production cutover

Before cutover

  1. Confirm production KYB is approved and operations is ready.
  2. Review payout, settlement, reserve, and support expectations for your region.
  3. Verify webhook URL ownership and production monitoring plan.

Production credentials

  1. Create production/live keys.
  2. Use minimal scopes for required actions.
  3. Register production webhook endpoints and secrets.
  4. Replace staging URLs with production hosts in code/config.

Final go-live checks

  1. Run one controlled low-value live transaction.
  2. Confirm production reconciliation and settlement visibility.
  3. Ensure live payout readiness and settlement timing are documented.
  4. Keep staging test keys/webhooks isolated; do not reuse in production.

Notes: API key scopes and webhook security

  • API keys currently support payment scopes (`payments:read`, `payments:create`).
  • The public API-key surface is limited to payment create, list, and read operations for now.
  • Webhook signing secrets are stored encrypted and never persisted in cleartext.
  • Webhook endpoints can optionally encrypt delivery bodies with x25519_aesgcm; generated private keys are shown once.
  • Each environment uses separate webhook keys and signing material.