creditcardprocessing.tv

What It Is

RapidCents is a payment gateway / payment API solution, with the source material mainly presenting its developer documentation. It covers use cases such as Google Pay, virtual terminals, payment links, hosted payment pages, subscriptions/installments, invoices, and e-contracts, targeting merchants that need online card-not-present transactions and invoice-based payment collection.

Core Capabilities

In terms of payment methods, RapidCents supports Google Pay, manual card entry, saved cards, and connections to Visa, Mastercard, Discover, and Amex. Google Pay uses ECv2 tokenization: merchants only need to forward the raw token through the server-side API, while RapidCents handles signature verification, Java Tink decryption, risk control, and submission to the card networks. The virtual terminal supports Sale, Auth Only, Force/Capture, and Refund, making it suitable for phone-based or back-office card-not-present transactions. Payment links can be shared by email or SMS and support bank cards, Google Pay, and optional 3D Secure.

Pricing and Settlement

The documentation does not disclose transaction rates, monthly fees, refund fees, chargeback fees, minimum commitments, or other pricing details. For settlement, the Sale section only mentions that funds are “immediately settled,” but it does not provide the actual payout timeline, currency coverage, or merchant withdrawal rules. As a result, merchants still need to confirm commercial costs and cash-flow details with the platform.

Compliance, Risk Control, and Integration

On compliance, the documentation emphasizes HTTPS, PCI DSS requirements for handling sensitive data, as well as Google Pay’s acceptable use policy, terms of service, and brand guidelines. However, it does not disclose payment licenses or regulatory registration information. A notable risk-control feature is that PAN_ONLY Google Pay transactions can trigger a 3DS step-up based on risk, and payment links also support 3DS initialization, authentication, and challenge flows. The API documentation is fairly detailed, including Bearer token authentication, business_id, separation between test and production environments, and examples for multiple endpoint types.

Pros, Cons, and Who It’s For

The advantages are a clear developer integration path and coverage of merchant operations scenarios such as payment links, subscriptions, invoices, and contracts. Google Pay keys are managed by the gateway, reducing integration complexity. The downside is that the publicly available information is mostly technical documentation, with limited details on pricing, supported regions, licenses, SLA, and support channels. It is better suited to merchants with development resources that need North American-style card payments and remote collection capabilities. For China-based teams, it is still necessary to verify direct website access, merchant onboarding eligibility, supported currencies, and local bank card support. Alternatives to compare include Stripe, Adyen, Checkout.com, Braintree, and PayPal.