No-code and module-led rollout
Use platform modules and hosted flows to get live quickly with minimal engineering overhead.
Documentation
Integration docs for checkout, direct APIs, SDKs, and launch readiness
Review integration paths, implementation guidance, compatibility, and technical references in one documentation index built for payment launches.
Overview
Start from the integration path that matches your operating model
The docs hub is structured to help teams choose between hosted checkout, direct APIs, invoice-based collection, and widget flows before they dive into lower-level references.
Custom build path
Choose direct APIs when checkout design, risk logic, or payment routing needs merchant-side control.
Operational references
Reference pages cover signatures, pingbacks, codes, and compliance requirements needed after launch.
Guidelines
Use the docs in this order to reduce integration churn
Choose an API model based on checkout ownership and launch speed.
Confirm market, payment method, and payout requirements before implementation.
Implement callbacks, signatures, and reconciliation hooks early.
Run technical and business review before pushing to production.
APIs
Core payment APIs
Recommended
Checkout API
Hosted checkout flow for cards, alternative payment methods, carrier billing, and prepaid methods through a single integration path.
- Best for teams that want the fastest path to production
- Works with redirect or embedded checkout experiences
- Fits existing commerce flows without rebuilding the payment UI
OverviewOne-time paymentsSubscriptions
Custom
Direct API
Server-to-server and tokenized payment APIs for merchants that need to build and control their own payment surfaces.
- Supports custom forms and merchant-hosted checkout logic
- Includes client-side tokenization and callback flows
- Designed for highly customized payment experiences
Brick DirectMobiamo DirectMINT Direct
Operations
Invoicing
Invoice creation and payment collection workflows for teams that want to get paid without building a checkout first.
- Create invoices manually or through an API
- Send payment links directly to customers
- Reuse the same payment coverage behind the invoice flow
Manage invoicesInvoicing API
Catalog
Widget API
Hosted multi-price-point payment widget with product inventory support for digital goods and recurring billing flows.
- Ideal for productized purchase experiences
- Supports digital goods and subscription models
- Lets users pick products and complete payment in one widget
Widget overviewDigital goods
SDKs
SDK and library entry points
Mobile SDK
Unified mobile payment tooling for native apps that need local payment access with a lighter integration path.
OverviewAndroid SDKiOS SDK
Server SDKs
Backend libraries and starter points for common languages used in payment operations and integration services.
PHPNode.jsPythonRubyJava.NET
Smart TV SDK
Payment support for TV-based commerce and living-room purchase experiences.
Smart TV payments
Unity SDK
Game-focused integration support for Unity-based payment flows and virtual goods programs.
Unity SDK
Modules & Platforms
Prebuilt platform coverage
E-commerce
ShopifyMagentoWixWooCommerceOpenCartPrestaShopShopware
Hosting / SaaS
WHMCSXeroXenForoBlestavBulletinIP.Board
Gaming
BuycraftEnjinMinecraft Market
Travel & Services
CubilisKigoCustom service platforms
API Compatibility
Product by integration surface
| Product | Widget | Checkout | Direct | Invoice | SDK |
|---|---|---|---|---|---|
| PayAlto | Yes | Yes | No | No | No |
| Brick | Yes | Yes | Yes | No | Yes |
| Mobiamo | Yes | Yes | Yes | No | Yes |
| MINT | Yes | Yes | Yes | No | Yes |
| Invoicing | No | No | No | Yes | No |
Reference
Reference topics that matter after integration starts
Client-side callback
Currency codes
Language codes
Payment system codes
Product inventory
Pingback
Custom parameters
PCI DSS compliance
Signature calculation
Widget errors
Questions
Need help choosing or implementing an API?
Use support for operational issues, and route technical integration questions through the implementation path so engineering teams can review the right context.