Common use cases
The following table lists typical requirements for different business types and recommended features:The following recommendations are for reference only. You can refer to Feature list for a complete feature list and flexibly combine them according to your actual needs.
| Business type | Typical requirements | Recommended features |
|---|---|---|
| Platform service providers | Payment service providers (PSP) or e-commerce platforms Provide services for multiple merchants, need to settle separately and share revenue with merchants | Merchant management + Order/Top-up mode + Allocate funds + Off-ramp |
| Advertising platforms Provide payment collection services for merchants. After merchants receive top-ups from end users, part of the funds is used for platform advertising, and the remaining funds can be withdrawn | Top-up mode + Merchant management (optional) + Allocate funds + Crypto payouts | |
| Merchants | Independent online stores Customers browse products, add to cart, and checkout | Order mode + Payment link (optional) + Off-ramp |
| Gaming/entertainment platforms Users purchase in-game points and items | Top-up mode (points) + Order mode (items) + Crypto payouts | |
| SaaS subscription services Users pay monthly/yearly service fees | Subscription mode or Order mode + Off-ramp | |
| B2B payment business Receive large payments from downstream enterprises | Top-up mode + Off-ramp | |
| Funds services | OTC settlement scenarios Open independent top-up addresses for customers, perform OTC settlement after top-up | Top-up mode + Counterparty management + Off-ramp |
| Card consumption fund settlement scenarios Open independent top-up addresses for customers, settle funds after consumption | Top-up mode + Crypto payouts |
PSP integration example
As a payment service provider (PSP), you need to provide payment collection services for multiple merchants and achieve automated revenue sharing. A typical integration process is as follows:- Development environment setup: Complete Prerequisites (create account, configure API key and webhook endpoint, deposit to Fee Station)
- Merchant management and fund configuration: Create merchants for each downstream merchant to achieve independent revenue and expense management.
-
Integrate payment collection: Collect payments through Order mode.
- When creating orders, set developer fees to achieve automated revenue sharing with merchants.
- (Optional) Use Payment links to quickly build payment pages for merchants.
- Fund management: Use the Allocate funds feature to adjust allocation between accounts (such as collecting developer fees or handling overpayment, underpayment, late payment, and other abnormal situations).
- Payouts: Supports Off-ramp and Crypto payouts. Off-ramp requires pre-configuring bank accounts in Destinations.
- Production environment launch: After testing is complete, refer to Production environment preparation to complete configuration and go live
Gaming platform integration example
As a gaming platform, you directly serve end-user players, with the main revenue source being player top-ups. A typical integration process is as follows:- Development environment setup: Complete Prerequisites (create account, configure API key and webhook endpoint, deposit to Fee Station)
- Merchant configuration: No need to create new merchants, just use the default merchant automatically created by the system (same name as your Cobo Portal team).
-
Integrate payment collection: Collect payments through Top-up mode
- Create a dedicated top-up address for each player
- Players use fixed addresses to top up, and the system automatically associates top-up records with the corresponding payer
- Query each payer’s top-up details through Payments App or API
- Payouts: Supports Off-ramp and Crypto payouts. Off-ramp requires pre-configuring bank accounts in Destinations.
- Production environment launch: After testing is complete, refer to Production environment preparation to complete configuration and go live