Frequently asked questions

Rainbow Pay is the trading name of RAINBOW PAY LIMITED (彩虹匯有限公司), a payment technology and money services company incorporated in Hong Kong in 2021 (Company No. 3040501).

It is licensed as a Money Service Operator under the AMLO (Cap. 615) and supervised by the Hong Kong Customs & Excise Department. It provides eligible businesses with online payment acceptance, hosted checkout, a payments API and business payouts.

No. Rainbow Pay is not a bank and does not take deposits. It is a licensed Money Service Operator under the AMLO (Cap. 615).

Card acceptance is provided through acquiring or processing arrangements with third parties, subject to merchant eligibility and scheme requirements.

Money Service Operator licences are listed on the public register maintained by the Hong Kong Customs & Excise Department. You can search it at the official register (opens in a new tab) using the company name RAINBOW PAY LIMITED.

Our Regulatory information page explains what the licence covers and what it does not.

Follow our complaints procedure or write to complaints@rainbowpay.hk. Tell us who you are, what happened, the relevant dates and any payment reference you have.

Do not send full card numbers, passwords or identity documents by email. We acknowledge each complaint, investigate it and reply in writing.

Registered businesses that sell goods or services online can apply. Each application is assessed on its legal structure, ownership, business model, products, customer markets and processing history.

Some business types cannot be supported under our risk policy or the rules of the card schemes and our acquiring partners. If you are unsure, contact sales with a short description of your business.

Onboarding has four stages. 1. Tell us about your business through the Get started form. 2. Compliance review, where we carry out KYB and KYC checks. 3. Integration, using Hosted Checkout or the API, tested in the sandbox. 4. Go live, once compliance, commercial and technical approval are all in place.

Availability depends on your merchant entity, customer markets and payment configuration. Contact Rainbow Pay for the current coverage applicable to your business.

Depending on your business, we may request a certificate of incorporation, business registration, your ownership structure, identification of directors and beneficial owners, proof of address, website and business model information, and processing history where applicable.

These documents are requested only through the secure onboarding process. Never send them through the forms on this website or by ordinary email.

No. Every application is subject to compliance review and to commercial and technical approval. We may decline an application, or approve it with conditions, based on the outcome of that review.

Pricing is tailored to each merchant. It depends on the payment methods you use, your volume, your markets and currencies, your integration model, your risk and compliance profile and your settlement requirements.

Contact sales to discuss a proposal for your business.

Rainbow Pay currently presents card payments through Visa, Mastercard, American Express, UnionPay and JCB and digital wallet payments through Apple Pay, Google Pay, AlipayHK and WeChat Pay for online checkout.

Availability is subject to merchant eligibility, integration configuration and market support. The methods enabled for your account are confirmed during onboarding. See Payment methods for details.

Yes, for eligible merchants. Visa and Mastercard card payments are available subject to merchant eligibility, market availability, scheme requirements and applicable acquiring or processing arrangements.

Apple Pay and Google Pay are available for eligible merchant configurations, subject to market, device, acquiring and payment setup requirements.

Availability depends on your merchant entity, customer markets and payment configuration. Contact Rainbow Pay for the current coverage applicable to your business.

Availability depends on your merchant entity, customer markets and payment configuration. Contact Rainbow Pay for the current coverage applicable to your business.

Settlement timing and settlement currency are agreed as part of your commercial terms.

Availability depends on your merchant entity, customer markets and payment configuration. Contact Rainbow Pay for the current coverage applicable to your business.

You can refund a payment in full or in part against its payment token, through the API. The refund status is reported to your callback URL like any other status change.

A refund is initiated by you. It is different from a chargeback, which the cardholder starts through their card issuer.

Dispute information is available through a list endpoint in the API. Respond to disputes within the deadlines set by the card schemes, and keep order, delivery and customer communication records to support your response.

Yes. Eligible businesses can send payouts through the API and receive status updates by callback. A balance endpoint shows the funds available.

Payout corridors and currencies are subject to availability. Availability depends on your merchant entity, customer markets and payment configuration. Contact Rainbow Pay for the current coverage applicable to your business.

Hosted Checkout: you redirect the customer to a payment page hosted by Rainbow Pay, and they return to your success or fail URL. Card details are entered on our page, not yours.

API integration: your server calls the Rainbow Pay API directly for payments, refunds, two-step payments, recurring payments and payouts. Sending raw card data from your own server requires Rainbow Pay approval and brings your systems into PCI DSS scope.

See the integration guides and the API documentation (opens in a new tab).

Yes. The sandbox emulates processing, so you can test payments, declines, refunds and callbacks without moving real money. Sandbox access is provided during onboarding.

Yes. Set recurring: true on the customer's first payment. When it is approved, the response includes a recurringToken, which you use to create later repeat payments without asking the customer to enter their card again.

You must have the customer's agreement to repeat charges and let them cancel. Recurring availability can vary by payment method.

Yes. Create the payment with needConfirmation, then confirm or decline it later through the API. This suits orders where the final amount or stock is checked before the charge is completed.

When a payment changes status (pending, approved or declined), Rainbow Pay sends a POST request to the callbackUrl you supplied. If your server does not answer with HTTP 200, the callback is retried.

Treat callbacks as signals, not as the only source of truth. Process them idempotently and confirm the final status through the API before fulfilling an order.

The API reference is public at docs.rainbowpay.hk (opens in a new tab). Sandbox credentials are issued during onboarding. Guides are on the developer pages and in the integration guides. For integration questions, write to support@rainbowpay.hk.

As a Money Service Operator, Rainbow Pay applies anti-money laundering and counter-terrorist financing controls required under the AMLO (Cap. 615). These include customer due diligence on merchants and their owners, sanctions screening, ongoing transaction monitoring and record keeping.

Merchants are reviewed at onboarding and on an ongoing basis. Read more on our Compliance page.

The Money Service Operator licence is issued under the AMLO (Cap. 615) and covers money services such as remittance. It is not a banking licence and it is not a card-acquiring licence. Card acceptance is provided through third-party acquiring or processing arrangements.

No. Hosted payment architectures may reduce the amount of payment data handled directly by a merchant. The merchant remains responsible for determining and validating its applicable PCI DSS obligations.