Payment infrastructure for merchants operating across high-growth markets
Accept payments, route checkout sessions, issue refunds, and manage payout and settlement operations from one Go-backed merchant platform.
Payments
Tracked
Completed
Settled
Success rate
Measured
Volume — all currencies
Merchant analytics preview
Product
Merchant workflows built around the active platform
The landing page now centers the shipped merchant, hosted checkout, and API surfaces instead of planned consumer or agent experiences.
Accept payments
Create payment sessions, track authorization states, and keep merchants inside one operational dashboard.
Hosted checkout
Use hosted checkout for payer collection while sensitive card entry stays inside secure hosted payment fields.
API and developer tools
Issue API keys, configure webhooks, and integrate with typed client helpers backed by the Go API.
Refund operations
Review payment details, initiate eligible refunds, and keep exception workflows visible for merchant teams.
Payouts and settlements
Plan payouts and settlement workflows, including USDT settlement where supported by the operating model.
KYB and compliance
Collect KYB documents, review business status, and preserve audit trails for sensitive operational changes.
Developers
API-first merchant operations without the hand-waving
Integrate payment creation, webhook delivery, idempotency, and typed client flows while dedicated public API docs continue to mature.
POST /v1/payments
Idempotency-Key: merchant-order-001
{
"amount": "125.00",
"currency": "USD",
"checkout": {
"mode": "hosted",
"return_url": "https://merchant.example/return"
},
"metadata": {
"order_id": "merchant-order-001"
}
}
webhook: payment.succeeded
signature: t=timestamp,v1=hmac_sha256(...)Markets
Corridor planning without unsupported claims
Market availability depends on operating model, partner readiness, payment-rail coverage, and compliance review. The page avoids regulatory and market-count claims that are not verified here.
Merchant onboarding
Active app surface
Hosted checkout routing
Active checkout surface
Expanded corridors
Roadmap and partner dependent
Pricing
Usage-based pricing for merchant payment operations
Use the contact route for pricing that reflects integration setup, merchant risk profile, payout workflows, and settlement needs.
Usage based
For merchants integrating hosted checkout, API payment creation, webhooks, and operational dashboards.
- Checkout session orchestration
- Payment and refund visibility
- API keys and webhooks
- Merchant team roles
Custom operations
For merchants that need payout methods, KYB review workflows, settlement operations, or corridor-specific support.
- KYB and compliance workflow support
- Payout and settlement planning
- Operational review paths
- Integration support scoping
Security
Controls for payment, merchant, and back-office workflows
Security copy is tied to implemented product controls and avoids unverified regulatory or licensing claims.
Email verification and merchant onboarding controls
Role-based merchant teams for owners, admins, developers, and viewers
Two-factor step-up for sensitive dashboard actions
Hashed API keys with revoke and expiry controls
Webhook signing with delivery logs and retry visibility
KYB document handling with attachment-only downloads
Audit logs for admin and merchant operations
Refund, payout, and settlement workflows separated by role
FAQ
Straight answers for merchant teams
Is Alpha DigiWallet focused on merchants or consumers today?
The active product surface is the merchant platform: registration, hosted checkout, API keys, webhooks, refunds, KYB, payout methods, and operational dashboards.
Does hosted checkout store card data in the web app?
Card entry is intended to stay inside secure hosted payment fields. The merchant app should orchestrate the session and status, not collect raw card data.
How should USDT settlement be described?
Settlement can be primarily in USDT where supported by the operating model. Alpha DigiWallet does not trade crypto or accept USDT as card payment tender.
Are public API docs complete?
The landing page introduces API concepts. Dedicated public API documentation is still a separate requirement.
What happens when the contact form is submitted?
The web app stores the inquiry in the Go-backed contact inquiry queue for admin follow-up. It does not send email.
What merchant operations are already represented?
The app includes Go-backed flows for auth, merchant organizations, API keys, webhooks, KYB, payments, refunds, payouts, settlements, support, and admin review.
Contact
Scope a merchant integration
Share your payment, checkout, refund, payout, or settlement requirements. We will get back to you shortly, or you can email contact@alphadigiwallet.com.