Payment API for Chinese cross-border sellers

A private, standardized checkout layer for legitimate export merchants.

RamboPay helps independent stores create payment links and API payments without sending full product names, SKU lists, detailed usage, or purchase catalogs to the payment channel.

Your store keeps the real product data; RamboPay submits only your configured lawful payment descriptor to the payment channel.

Apply for merchant access Read integration docs

Dedicated channels Descriptor minimization Signed webhooks Merchant review

RamboPay Gateway

Channel descriptor Merchant Invoice Payment

Private merchant order B2B-20260723-8819

Full SKU / purchase catalog Not sent to channel

{
  "amount": "499.00",
  "currency": "USD",
  "merchant_order_id": "B2B-20260723-8819",
  "payment_descriptor": "Merchant Invoice Payment"
}

2,000+merchant-scale architecture

8supported currencies

99.9%target API uptime

HMACsigned webhook security

The real value: payment-description minimization

Let payment channels see a lawful payment summary, not your full product name, SKU, usage detail, or purchase catalog.

Your store keeps the real order, invoice, SKU and fulfillment evidence. The payment channel receives a concise, lawful order summary such as Cross-border Ecommerce Order or Merchant Invoice Payment.

Core product capability

Custom channel-facing product information: merchants decide what the payment channel sees.

For cross-border merchants, product titles, SKUs, purchase lists, customer usage, supplier details, and quotation data are commercial assets. RamboPay separates real order details from channel-facing payment information.

Hidden

Full product name

Do not submit sensitive product titles as payment titles.

Hidden

SKU / Model

Keep SKU, model, and supply-chain codes inside the merchant system.

Hidden

Detailed usage

Customer usage, customization details, and service scope stay private.

Custom

Custom descriptor

Channels see descriptors like Merchant Invoice Payment or Digital Service Order.

Information flow after integration

Real order data and channel-facing feedback are handled separately.

01Buyer orders on the store; full product detail stays in merchant system.

02Merchant calls RamboPay API with order ID, amount, and custom descriptor.

03Payment channel sees a standard descriptor, not SKU or purchase catalog.

04After payment, signed webhook notifies merchant fulfillment system.

B2B export orders

Procurement categories, supplier details, and quote sheets stay in the merchant system while the payment side receives a standard descriptor.

Custom service payments

Scope, customer requirements, and delivery details do not need to become payment titles.

Digital products and SaaS

Use Digital Service Order or Subscription Payment while mapping entitlements privately.

Independent-store API

Integrate once for checkout, payment states, webhooks, dashboard operations, and channel expansion.

Merchant use cases

Designed for merchants who care about product and buyer privacy.

B2B wholesale: avoid exposing procurement categories and supplier details.

Custom products: avoid exposing customer usage and custom parameters.

Digital products/services: avoid exposing exact product names and account usage.

Independent stores: show payment channels a unified order summary.

Dedicated channel capability

Dedicated payment strategy for approved merchants.

RamboPay is not a public payment button. It is a reviewed channel, standardized descriptor, risk-control, and API-management layer for cross-border merchants.

PayPalDedicated review

CardsAcquirer partner ready

WebhookHMAC signed

Compliance statement

Protect lawful transaction privacy. Never package illegal transactions.

Privacy is supported. Illegal transactions, prohibited goods, deceptive descriptions and attempts to bypass payment network rules are not allowed.