RamboPay

RamboPay Knowledge Base

Privacy-aware payment layer for WooCommerce merchants

Privacy-aware payment layer for WooCommerce merchants: a practical guide to RamboPay integration, product transaction privacy, custom payment descriptors, API workflows, and lawful compliance boundaries.

The core problem

Privacy-aware payment layer for WooCommerce merchants is about keeping full product names, SKUs, usage details, purchase lists, supplier information, and buyer privacy inside the merchant's own order system instead of exposing them to payment channels.

How RamboPay helps

With RamboPay, merchants create payments through an API and submit amount, currency, merchant order ID, return URL, webhook URL, and a custom payment descriptor. The channel sees a lawful concise summary while the real order stays with the merchant.

Where it applies

This topic is useful for 独立站 scenarios such as B2B exports, independent stores, custom services, digital products, SaaS subscriptions, inquiry invoices, and overseas business services.

Integration focus

Developers should configure API keys, webhook secrets, return_url, notify_url, merchant_order_id, and payment_descriptor. After payment succeeds, RamboPay sends a signed webhook so merchants can verify and fulfill safely.

Compliance boundary

Product transaction privacy is not transaction disguise. RamboPay does not support illegal transactions, prohibited goods, fraud, laundering, gambling, infringing goods, deceptive descriptions, or payment-network bypassing.

Practical recommendation

Start with standard descriptors such as Merchant Invoice Payment, Cross-border Ecommerce Order, Digital Service Order, or Subscription Payment, then build descriptor rules and review workflows for each business line.

FAQ

Does RamboPay delete real order details?

No. Real order details should remain in the merchant system. RamboPay helps control the channel-facing payment summary.

Is this bypassing payment-channel risk controls?

No. The platform supports lawful commercial privacy, not prohibited goods, deceptive descriptions, or disguised transactions.

Apply for merchant access View API docs