Every performance claim on falconpay.online — UPI success rates, rail-specific rates, uptime, settlement volume, API latency — is backed by a documented measurement methodology. This page explains exactly how each number is measured, the sample, the window, what's excluded, and how often the number is refreshed. If a claim appears anywhere on our site and isn't documented here, treat that as a bug and tell us.
Last updated: 18 April 2026 · Next review: 18 July 2026
This is the most frequently cited number on our site. It reflects the transaction-level success rate of P2M UPI transactions routed through FalconPay's acquiring relationships for licensed real-money gaming, fantasy sports, and adjacent high-risk merchants in India.
| What we measure | Successful completion rate of P2M UPI intent transactions from the user's banking app back to the merchant callback, reconciled against acquiring-bank settlement reports. |
| Sample size | ≥ 10,000,000 transactions in the rolling window (updated quarterly). |
| Measurement window | Rolling 90-day window, refreshed weekly internally and quarterly on the marketing site. |
| Scope — included | Licensed merchant accounts operating for ≥30 days, transactions routed via FalconPay's direct acquiring rails, production mode only. |
| Scope — excluded | Test-mode transactions, merchants in the first 30 days of vintage (calibration period), merchants under regulatory hold or compliance review, transactions failing at the user's bank before reaching an acquiring rail (e.g., insufficient balance, blocked device). |
| Data source | Acquiring-bank settlement reports reconciled against our internal transaction ledger. Bank-side discrepancies are resolved weekly before the number is refreshed. |
Honest caveat. Per-merchant success rates vary. Onboarding includes a 2-week calibration period during which our router learns acquirer-bank health patterns specific to the merchant's customer segment. During calibration, success rates typically range 93–96% before stabilising above 98%. Merchants with player bases heavily concentrated in specific regional banks may see rates slightly below 98.5% depending on those banks' real-time health.
These rail-specific rates appear primarily on the regional pages (India, Brazil, Europe, LATAM) and in country-specific sections of the comparison pages. The measurement approach is identical to the UPI rate above, with the rail-appropriate sample and acquiring relationship:
| Rail | Measurement basis |
|---|---|
| 🇲🇽 Mexico SPEI (97.8%) | Real-time SPEI transactions, direct acquiring via CNBV-regulated partners, rolling 90-day window, sample ≥ 4M transactions. |
| 🇨🇴 Colombia PSE (96.4%) | PSE bank-redirect transactions across major Colombian banks, rolling 90-day window, sample ≥ 2M transactions. |
| 🇦🇷 Argentina Mercado Pago (95.1%) | Mercado Pago wallet redirects, rolling 90-day window, sample ≥ 3M transactions. Excludes periods of acquirer-side outage. |
| 🇵🇪 Peru PagoEfectivo (88.3%) | Voucher-code completion rate (player receives code → pays at BCP/Interbank branch). Cash-rail completion is structurally lower than real-time rails. Sample ≥ 800K voucher generations. |
| 🇨🇱 Chile Webpay (97.2%) | Webpay Plus card acquiring via Transbank, rolling 90-day window, sample ≥ 2M transactions. |
| 🇧🇷 Brazil PIX (98.5%) | PIX instant transactions via direct acquiring partners, rolling 90-day window, sample ≥ 8M transactions. |
| 🇪🇺 Europe SEPA card (99.1%) | 3DS2-authenticated card transactions across 36 SEPA countries, rolling 90-day window, sample ≥ 6M transactions. |
Honest caveat. PagoEfectivo's 88.3% reflects the nature of cash rails — not every player who generates a voucher walks to a branch to pay. The real-time rails (SPEI, PSE, MP, Webpay, PIX) are directly comparable to UPI; the cash rail is a different instrument and should be compared against other cash rails, not against UPI.
| What we measure | Availability of the primary API and processing gateway, measured across synthetic health checks from three independent geographic probes plus internal service-level endpoints. |
| Measurement window | Rolling 12-month window. |
| Included in downtime | All unplanned outages affecting the primary API endpoint, including partial degradations where error rates exceeded 5% for >60 seconds. |
| Excluded | Scheduled maintenance communicated ≥48 hours in advance via our status page and direct email to account technical contacts. Third-party upstream outages affecting only one specific rail (reported as rail-level incidents, not gateway downtime). |
| Data source | Synthetic monitoring logs + internal observability platform, cross-verified against customer-reported incidents. |
99.98% over 12 months permits approximately 105 minutes of unplanned downtime. Our actual measured performance has trended marginally better than this over the most recent windows, but we publish the SLA figure rather than the current peak to set honest expectations.
| What we measure | 95th-percentile server response time on the core /payin and /payout endpoints, measured from receipt of the request at our edge to dispatch of the response. |
| Sample | All production traffic in the measurement window. |
| Measurement window | Rolling 7-day window. |
| Excluded | Client-side network latency (not under our control), cold-start penalties on the first 0.1% of requests after deploy, and requests that trigger extended third-party calls (acquirer handshake, 3DS challenge) — those are measured separately in the acquirer-side latency breakdown. |
| Data source | Internal observability spans on the edge gateway. |
| What we measure | Cumulative USD-equivalent gross transaction volume successfully processed through FalconPay's primary gateway since launch. |
| FX basis | Non-USD transactions converted to USD at the spot rate on the transaction date. |
| Included | Successfully settled pay-in and payout transactions across all rails. |
| Excluded | Failed transactions, reversed/refunded transactions, test-mode transactions. |
| Update cadence | Quarterly. |
| What we measure | Time elapsed between receipt of a complete merchant application package and the issuance of an underwriting decision. |
| "Complete" means | Corporate registration docs, ownership disclosure to the 25% UBO threshold, a valid gaming or business licence where the vertical requires one, platform compliance information, and a signed MSA draft or approved commercial terms. |
| Sample | Licensed merchants submitting complete applications. Does not include incomplete applications awaiting missing documents. |
| Variance | Most decisions land in 48–72 hours. Complex cases (multi-jurisdictional licensing, unusual ownership structures, enhanced due diligence triggers) can take longer and are communicated upfront. |
Quarterly refresh. Every number above is reviewed at least once per quarter. The "last updated" date at the top of this page reflects the most recent review. Historical versions are preserved in our internal audit trail.
If a number moves. If a measured rate degrades materially for more than a single measurement window, we update this page and the corresponding marketing pages before the next scheduled review. We'd rather publish a slightly lower real number than defend a higher aspirational one.
Independent verification. Our compliance and security audit programme (PCI DSS Level 1, SOC 2 Type II, ISO 27001) includes attestation on the operational controls behind these measurements. Auditor reports are available under NDA via [email protected].
Challenge the numbers. If you find a claim on our site that contradicts this page, or you think a methodology isn't conservative enough, write to [email protected]. We treat every correction as a bug and publish the fix.