Cowrie Research

redotpay-primary-sources-2026-05-07

5 min read

RedotPay primary-source snapshot

Fetched: 2026-05-07 UTC

1) RedotPay Connect overview

Source: https://redotpay.readme.io/

Selected excerpts from the official docs:

This online payment solution lets your website or app (e‑commerce, SaaS, digital goods, and more) accept stablecoin payments from customers, while you receive direct payouts in your local currency.

Quickly add a crypto payment option with our checkout SDK via OpenAPI.

Processing fees are much lower than traditional payment gateways and card networks (often below 2%).

RedotPay currently offers standard T+1 settlement in USD for merchants. Support for other local currencies and cryptocurrencies is being prepared.

Payments are mainly made in stablecoins and settled to you in USD.

Additional signals from the source:

  • The docs position RedotPay Connect as a merchant-facing stablecoin acceptance stack rather than merely a consumer crypto card app.
  • The combination of stablecoin acceptance, OpenAPI access, checkout SDK language, and merchant settlement framing suggests RedotPay is operating both a spend app and a merchant settlement layer.

2) Payment integration model

Source: https://redotpay.readme.io/reference/payment

Selected excerpts from the official guide:

This guide details the two primary payment integration flows offered by RedotPay Connect.

Payment via Paylink: Generates a payment link. The user is redirected to a RedotPay-hosted page to complete the payment.

Payment via Open-API: Retrieves payment information (URL/QR Code) directly via API to complete the payment within the merchant’s context.

Choose Payment via Paylink for rapid integration, simpler maintenance, and if redirecting users to a hosted payment page is acceptable.

Choose Payment via Open-API for a deeply customized payment experience, keeping users on your site, or for integrating with DApps.

Additional signals from the source:

  • This is strong evidence that RedotPay Connect is more like a payment-orchestration layer than a one-off hosted checkout page.
  • The docs explicitly cover merchant-server responsibilities, QR-code flows, deeplinks, callbacks, and custom checkout logic.

3) API security and callback verification

Source: https://redotpay.readme.io/docs/redotpay-api-request-signature-and-verification-guide

Selected excerpts from the official guide:

In Production and Gray environments, all API requests containing body parameters must be signed using the SHA256withRSA algorithm.

Upload your public key to the RedotPay merchant platform.

Obtain RedotPay’s public key from the RedotPay platform for callback signature verification.

The private key must be securely stored on your server and never leaked.

Regularly rotate keys (recommended every 12 months).

Additional signals from the source:

  • The public docs go beyond simple REST reference material and expose concrete operational guidance around signatures, callback verification, replay-window handling, and key rotation.
  • That level of first-party operational detail is a useful sign that RedotPay Connect is meant for real merchant production integrations.

4) Open API v2 migration surface

Source: https://redotpay.readme.io/docs/open-api-v2-upgrade-guide

Selected excerpts from the official guide:

/openapi/v2/order/payment-method: Retrieves details (URL, QR code, variants) of the payment method associated with an order.

The v1 endpoints /preOrder/create and /order/create are merged in v2, primarily using the single /order/create endpoint.

v2: CreatePayOrderResponse (orderSn, outerOrderSn, h5Url, webUrl, appUrl, paymentMethods)

In a custom checkout page, call /order/payment-method to get the URL/QR code/deep link and paymentVariants for a specified methodId.

Additional signals from the source:

  • The v2 guide reinforces the control-plane reading: order creation, payment-method retrieval, query, refund, and migration behavior all sit inside one merchant payment backend.
  • The response model for payment variants, QR codes, deeplinks, and unified wrappers suggests RedotPay is standardizing several payment experiences under one API.

5) Consumer app services and wallet/card surface

Source: https://helpcenter.redotpay.com/en/articles/11070044-redotpay-services-and-features

Selected excerpts from the official help center:

RedotPay is a stablecoin-based payment app that lets you use your cryptocurrency just like traditional currency.

Stablecoin-Based Cards: Issue virtual and physical cards for global spending.

All-in-One Wallet: Securely hold and manage multiple types of digital and local currency in a single app.

International Availability: Services are available in over 158 countries.

ATM Withdrawals: Fast withdrawals supported via physical cards.

Additional signals from the source:

  • The help center shows the consumer product is not only a card wrapper; it includes wallet balances, deposits, withdrawals, and global usage.
  • This broader spend stack matters because it explains how RedotPay can bridge merchant acceptance and user spending inside one brand.

6) Consumer onboarding and funding flows

Source: https://helpcenter.redotpay.com/en/articles/11008771-how-to-get-a-redotpay-card

Selected excerpts from the official help center:

Follow these steps to get your RedotPay stablecoin-based card ready for payments.

Complete identity verification in the app.

Add crypto to your RedotPay account using Binance Pay, on-chain deposits, or buy crypto with a credit card (Android only).

Apply for your card. In the app, go to [Card] and apply for a virtual or a physical card.

Additional signals from the source:

  • The onboarding flow reveals a regulated consumer payments stack layered on top of crypto deposits and card issuance.
  • The supported funding methods suggest RedotPay sits between on-chain balances, exchange-linked deposits, and card-spend rails.

7) International transfer rail

Source: https://helpcenter.redotpay.com/en/articles/11325255-how-redotpay-international-transfer-works

Selected excerpts from the official help center:

It’s an easy way to turn your crypto (like USDT, USDC, or BTC) into local currency and send it straight to bank accounts or e-wallets.

Some popular routes—like Nigeria and Brazil—currently have no transfer fees.

Usually, no. Most local transfer networks (like Pix, SPEI, or SEPA) don’t charge extra fees.

You can send USD and EUR transfers to other people.

Additional signals from the source:

  • This transfer feature makes RedotPay look broader than a card-plus-wallet product; it also exposes an off-ramp and cross-border payout layer.
  • Mention of Pix, SPEI, and SEPA is especially useful because it shows RedotPay is explicitly interfacing with recognizable local payment rails.

Notes

  • RedotPay is best cataloged as a stablecoin spend-and-merchant-payments control plane / card-and-wallet infrastructure / crypto-to-fiat settlement layer.
  • No canonical standalone RedotPay whitepaper or litepaper surfaced in this pass.
  • The clearest primary sources were the RedotPay Connect docs plus the consumer help-center articles for services, card onboarding, and international transfer behavior.

Graph View