COMPANY detail
SQRIL Pay QR codes like a local across Asia, Africa and Latin America
PAYER FEATURE OVERVIEW.
PROJECT NAME
SQRIL 
SUPPORTED ASSETS
?
Cryptocurrencies and stablecoins accepted for payments.
USDT, USDC
BLOCKCHAIN SUPPORT
?
Blockchain networks supported for processing payments.
Ethereum
WALLET COMPATIBILITY
?
Wallets that can be used to make payments.
SQRIL mobile app
QR TYPE
?
Supports static QR codes, dynamic QR codes, or both.
Static: YES — Dynamic: YES
PAYMENT SPEED
?
Typical time required for a payment to be confirmed.
NOT DISCLOSED
FEES FOR PAYERS
?
Fees charged to users when making payments.
Low fees
USER KYC
?
Whether identity verification is required to use the service.
YES
CUSTODY MODEL
?
Defines who controls and holds users' funds.
Custodial
MOBILE APP REQUIRED
?
Whether a dedicated mobile app is needed to pay.
YES
PAYMENT METHODS
?
Supported payment methods such as QR, NFC, or deep links.
QR: YES — NFC: NOT DISCLOSED
RECURRING PAYMENTS
?
Whether subscription and recurring payments are supported.
NOT DISCLOSED
GEOGRAPHIC AVAILABILITY
?
Countries or regions where the service is available.
Philippines, Vietnam, Thailand, Cambodia, Brazil, Argentina, Colombia, Peru, Bolivia, Kenya, Tanzania, South Africa
Last Updated: Jul 5, 2026
- World's first cross-border QR code payments API to bridge stablecoins with incompatible national QR schemes across Asia, Africa, and Latin America
- Backed by Tether (USDT issuer) — deep stablecoin liquidity and credibility for conversions at scale
- Payer loads wallet with stablecoins (USDT/USDC); no need to hold any local fiat currency before travel or spending
- National QR codes (QR Ph, VietQR, Thai QR, KHQR, PIX/Brazil QR) are decoded at scan time via the decodeQr API endpoint
- Regulated under Canadian law through 1421069 B.C. LTD; data stored on US servers
- Also supports bank/ewallet transfers to the same countries when no QR code is present — fallback to account-number payments
- Full KYC with biometric face scan required before any transaction; machine/device fingerprinting for fraud prevention
MERCHANT FEATURE OVERVIEW.
PROJECT NAME
SQRIL
PAYMENT CHANNELS
?
Where payments can be accepted: online, in-store, or both.
Online: YES — In-Store: YES
SUPPORTED ASSETS
?
Cryptocurrencies and stablecoins merchants can accept.
Fiat settlement in local currency
FIAT SETTLEMENT
?
Whether crypto payments can be settled in fiat currency.
YES
SETTLEMENT CURRENCY
?
Currencies merchants receive after payment settlement.
PHP, VND, THB, KHR, BRL, ARS, COP, PEN, BOB, KES, TZS, ZAR
SETTLEMENT SPEED
?
Typical time required to receive settled funds.
NOT DISCLOSED
MERCHANT KYC
?
Whether business verification is required to accept payments.
YES
POS INTEGRATION
?
Support for integration with physical point-of-sale systems.
QR code-based
E-COMMERCE INTEGRATION
?
Supported integrations with online store platforms.
YES
API ACCESS
?
Whether developers can build custom integrations using APIs.
YES
PAYMENT LINKS
?
Ability to create shareable payment links without coding.
NOT DISCLOSED
INVOICING
?
Ability to create and manage payment invoices.
NOT DISCLOSED
REFUND SUPPORT
?
Whether merchants can issue refunds through the platform.
YES
WEBHOOKS
?
Real-time notifications for payment and status updates.
NOT DISCLOSED
GEOGRAPHIC AVAILABILITY
?
Countries or regions where merchants can use the service.
Philippines, Vietnam, Thailand, Cambodia, Brazil, Argentina, Colombia, Peru, Bolivia, Kenya, Tanzania, South Africa
Last Updated: Jul 5, 2026
- Zero infrastructure change for merchants:
existing national QR codes (QR Ph, VietQR, Thai QR, PIX, etc.) are automatically compatible with SQRIL's scanning API
- API-first integration flow: registerCustomer → decodeQr → getQuotation → executePayout; sandbox environment at stg-api.sqril.io for testing
- Crypto-to-fiat conversion is entirely invisible to merchants — they always receive local fiat currency in their bank account or ewallet
- Explicitly positioned as a merchant payment tool, NOT a money remittance service — ToS prohibits use for transfers without underlying goods or services
- Tether backing provides settlement confidence: deep stablecoin liquidity means reliable conversion even at high transaction volumes
- Manual business onboarding via contact form (business name, website, country) suggests early-stage self-serve merchant portal not yet launched
- SDK examples in Python, JavaScript, Go, Ruby, Java, PHP, C#, Swift ship in the developer docs
THE REAL STORY.
PROS
[ STRENGTHS ]
- First cross-border QR payments API for emerging markets
- Tether backing provides stablecoin liquidity and credibility
- National QR scheme integration — existing merchant QR codes already compatible
- Full REST API with sandbox environment for developers
- Comprehensive KYC/AML compliance with biometric verification
- Broad coverage spanning Asia, Africa, and Latin America
CONS
[ LIMITATIONS ]
- Fee structure and limits not publicly disclosed (login-gated)
- Mobile app dependency — no web-based QR scanner
- Custodial model — users do not control private keys
- Heavy KYC (ID + biometric scan) may deter privacy-conscious users
- No recurring payment or webhook features publicly documented
GENERAL QUESTIONS.
SQRIL markets "low fees" and "best possible exchange rates" but exact fee percentages are not publicly disclosed. The platform generates revenue through a spread on currency conversion (stablecoin to local fiat) rather than explicit transaction fees. A fees page is referenced in the Terms of Service but requires a logged-in account to access.
Settlement speed is not explicitly stated in public documentation. The platform processes stablecoin-to-fiat conversion at transaction time, and local settlement likely follows the national payment rail's standard timeline (typically instant to T+1 depending on the country). The Terms of Service acknowledge dependency on third-party banking timelines.
No recurring or subscription payment features are mentioned in the marketing site, API documentation, or Terms of Service. The current API focuses on one-time QR code payments and payouts (registerCustomer → decodeQr → getQuotation → executePayout).
