Gr4vy ReviewIs It the Right Payment Solution for Your iGaming Business?
Adequate
Gr4vy is a cloud-native payment orchestration platform founded in 2020 by John Lunn, the former head of developer relations at PayPal and Braintree. The defining choice: every merchant gets a dedicated single-tenant instance on Google Cloud rather than sharing a multi-tenant SaaS. That gives the operator full data isolation, BYOK key management and a configurable region for sovereignty rules. The platform connects to 400+ payment methods and anti-fraud providers through one API. PCI DSS Level 1 and SOC 2 Type 2 certified. Pricing is a predictable monthly instance cost plus a small per-transaction fee, not a flat percentage — Gr4vy says this is cheaper than rivals at scale but the company does not publish numbers. $27.2M raised across a Series A and a 2022 extension at a $115M valuation. About 57 employees. Marquee enterprise clients include Trek (signed March 2025), Grammarly (June 2025), Wpay/Woolworths Group, JustGiving, Ding and ELEVEN Sports. Here is the part that matters for this site: Gr4vy's own FAQ lists unlicensed gaming among prohibited verticals, there is no published gambling case study, no responsible gaming module, no MGA or UKGC support material, and the case studies that touch sport (PlayHQ, ELEVEN Sports) are streaming and grassroots-sports payments, not real-money betting. For iGaming operators specifically, Gr4vy is not built for you. For an enterprise non-gambling merchant who wants single-tenant control of a routing layer and is willing to pay enterprise rates, Gr4vy is one of the better-engineered orchestrators in the market.
Quick Info
iGaming Score
Our iGaming Score: 5.6/10
Weighted scoring across six criteria
| Criterion | Weight | Score | Rating |
|---|---|---|---|
| iGaming Fit No gambling clients, no MGA/UKGC material, FAQ excludes unlicensed gaming. The iGaming fit is essentially zero | 25% | 3.5 | Weak |
| Geographic Coverage Global through 400+ connected payment methods. Single-tenant instances can be deployed to any Google Cloud region for data residency | 20% | 10.0 | Best-in-class |
| Security & Compliance PCI DSS Level 1, SOC 2 Type 2, GDPR, CCPA. Strong baseline but no acquiring or gambling licenses — those sit with connected PSPs | 20% | 5.0 | Adequate |
| Fees & Pricing Custom infrastructure + per-tx model. No public numbers. Predictable monthly cost is a real benefit at scale but lack of pricing transparency is a buyer disadvantage | 15% | 3.5 | Weak |
| Tech & Integration Cloud-native single-tenant architecture is the genuine differentiator. SDKs in TypeScript, Go, Swift, Kotlin. Native 3DS2 in Secure Fields | 10% | 7.0 | Strong |
| User Trust No Trustpilot profile. 5/5 from 1 G2 review is meaningless. Reputation has to be inferred from the client list, not from review-site signals | 10% | 5.0 | Adequate |
| Overall | 100% | 5.6 | Adequate |
We score each provider on six criteria using a 1 to 10 scale. iGaming Fit carries the most weight at 25% because that is what matters most for gambling operators. Geographic Coverage gets 20%. Security and Compliance, Fees and Pricing, and Tech and Integration each get 15%. User Trust rounds it out at 10%. The final score is a weighted average of all six.
Score Explanation
iGaming Fit drags everything down: Gr4vy's FAQ explicitly excludes unlicensed gaming, the public client list contains zero real-money gambling operators, and there is no responsible gaming tooling. For an iGaming-focused buyer this is the wrong product regardless of how well the rest of the platform scores. Geographic Coverage reflects 400+ connected methods plus the unusual ability to deploy a dedicated instance to a specific Google Cloud region, which is useful for Australian, EU and UK data-residency requirements. Security & Compliance is well-supported by PCI DSS Level 1 and SOC 2 Type 2 — most orchestrators stop at PCI. Fees take the standard orchestrator penalty: the headline routing fee prices only the orchestration layer, and PSP costs sit on top, so the all-in cost is whatever your connected PSPs charge plus Gr4vy. Tech & Integration is the strongest dimension: cloud-native single-tenant design is genuinely differentiated versus the multi-tenant approach of Corefy, Primer and IXOPAY. User Trust is a question mark because Gr4vy is too small and too B2B to generate meaningful Trustpilot or G2 volume.
Who Is Gr4vy Best For?
Weighted scoring across six criteria
Recommended For
Enterprise merchants requiring data sovereignty. Enterprise merchants in regulated non-gambling verticals where data residency is a hard requirement. Gr4vy's single-tenant Google Cloud deployment lets you pin the instance to an EU, UK, US or Australian region, with BYOK key management. Most orchestrators run multi-tenant SaaS where you cannot control where data sits. For an Australian retailer answering to APP data localization, or a European fintech handling GDPR sensitivity, this is a real operational benefit.
Teams wanting dedicated single-tenant infrastructure. Teams that want a routing layer architecturally separated from other merchants. In a multi-tenant orchestrator, you share infrastructure, you inherit noisy-neighbor latency, and a security incident on another customer's tenant theoretically touches yours. Gr4vy is the only orchestrator in our database built on dedicated cloud instances per merchant. That isolation has a cost — slower provisioning, higher minimum spend — but for security-conscious enterprises it is the differentiator.
Multi-PSP enterprises in non-gambling verticals. Multi-PSP enterprises processing across non-gambling verticals: e-commerce, OTT streaming, edtech, nonprofit, retail, crypto. Trek (cycling retail), Grammarly (SaaS), Wikimedia (nonprofit), Wpay (Woolworths grocery), Ding (mobile top-up), ELEVEN Sports (OTT streaming) are the reference clients. If your business model matches one of those shapes, the case studies are directly relevant.
Operators needing region-specific deployment. Operators who value predictable infrastructure pricing over flat percentage fees. Gr4vy quotes a monthly instance cost plus a small per-transaction fee, which scales more linearly than the 0.2-0.7% routing fees of Primer or Corefy at high volumes. At enterprise scale (Trek, Grammarly, Woolworths volume), this pricing model is cheaper. At smaller volumes, the fixed instance cost is overhead.
Not Recommended For
iGaming and online gambling operators. Online gambling operators. This is the headline point for readers of this site. Gr4vy's FAQ explicitly lists unlicensed gaming in its prohibited verticals. There are no MGA, UKGC, Curacao or any other gambling license partners in the materials. There is no responsible gaming module. There is no published case study with a real-money betting, casino or poker operator. The two sports-adjacent customers (PlayHQ for amateur sports payments, ELEVEN Sports for OTT video subscriptions) are not gambling. If you operate a licensed online casino or sportsbook, look at Corefy, IXOPAY, Finera or direct iGaming PSPs like Nuvei and Paysafe instead.
Small and mid-market merchants. Small and mid-market merchants. Gr4vy is sales-led, custom-quoted and built around a dedicated per-merchant cloud instance. The economics work when you spread that fixed instance cost across enterprise transaction volume. At $250k or $500k monthly volume, you will pay more than Corefy or Primer for the same functionality. Below seven-figure monthly volume, Gr4vy is overbuilt.
Operators wanting direct acquiring. Operators who want a single provider doing both processing and routing. Gr4vy does not process payments. You bring PSP contracts (Adyen, Checkout.com, Stripe, etc.) and Gr4vy routes between them. For operators who want to consolidate at one acquirer with built-in smart routing, Nuvei, Adyen and Checkout.com do that natively without the orchestration tax.
Teams needing fast, self-serve onboarding. Teams that want self-serve onboarding and immediate go-live. Gr4vy's enterprise model means a sales call, contract negotiation, KYB, instance provisioning, PSP credential collection and a 2-4 week onboarding before the first transaction. Compare that to Stripe-style sign-up-and-integrate-in-an-afternoon. Gr4vy is not built for that velocity.
Geographic Coverage
Supported regions and market focus
Regions
Coverage Analysis
Global reach through 400+ connected payment methods and anti-fraud providers. The unusual feature is regional deployment: each Gr4vy instance is provisioned to a specific Google Cloud region, which means the data plane (vaulted tokens, transaction records, PII) physically sits in that region. Reference deployments exist in the US, EU, UK, Australia and Asia. Latin America and Africa coverage exists through connected PSPs but is not Gr4vy's strongest region.
Regional Breakdown
For iGaming readers the geographic angle does not really apply — the platform does not target gambling — but the residency story matters in other regulated industries. An Australian merchant subject to APP standards can deploy a Sydney-region instance. A German fintech can pin to Frankfurt for BaFin and GDPR concerns. EU data localization rules can be satisfied without trying to negotiate them with a multi-tenant SaaS vendor. Operators in markets with sovereign-cloud requirements (Indonesia, India, Saudi Arabia) are a fit for the single-tenant model where multi-tenant orchestrators are not.
Key Features for iGaming Operators
Products, payment methods, and verticals
Key Products
Orchestration platform, Vault (tokenization), Optimize (smart routing), Checkout, Analytics
One core product — the payment orchestration platform — broken into modules: Acceptance (card and alternative method routing), Checkout (hosted checkout and Secure Fields), Optimize (smart routing, failover, geo-optimization, fraud-aware routing), Vault (network-level tokenization and PSP-agnostic data portability) and Analytics (real-time dashboards and reporting). The unifying architectural choice is single-tenant deployment per merchant on Google Cloud, which Gr4vy calls payment IaaS rather than payment SaaS.
Payment Methods
400+ payment methods through one universal API. Cards (Visa, Mastercard, Amex, JCB, Discover and local schemes), digital wallets (Apple Pay, Google Pay, PayPal), BNPL (Affirm, Afterpay, Klarna via PSPs), bank transfers (SEPA, ACH, iDEAL, PIX, Trustly), gift cards, prepaid and crypto via connected providers including BitPay. Mastercard Click to Pay was added through a 2025 partnership. The 400+ count is total connections — what is actually available to your operation depends on which connections your enterprise sales rep enables.
Verticals
Non-gambling enterprise: e-commerce, retail, OTT streaming, edtech, nonprofit, healthcare and crypto. Published case studies include Trek (cycling retail unifying online and in-store), Grammarly (SaaS), Wpay/Woolworths Group (powering Australia's largest retailer's payments platform), JustGiving (charity fundraising), Ding (mobile top-up across 140+ countries), ELEVEN Sports (OTT sports streaming), FuturHealth (healthcare), PlayHQ (grassroots sports admin), Baby Bunting (children's retail), Mattilda and Setplex. iGaming, online betting, casino and poker are explicitly out of scope per the FAQ. The sports-themed clients are streaming and amateur-sports admin, not real-money gambling.
| Feature | Status | Details |
|---|---|---|
| Deposit Processing | 400+ payment methods and anti-fraud providers via single integration payment methods, | |
| Withdrawal / Payout | ||
| Instant Withdrawals | ||
| KYC / AML Built-in | Full auto | |
| Chargeback Protection | Depends | |
| Multi-Currency | 150+ fiat via PSPs, crypto via PSPs | |
| API Integration | Single API + SDK | |
| Local Payment Methods | 400+ payment methods and anti-fraud providers via single integration methods across multiple categories | |
| iGaming Specialization | Single-tenant cloud architecture + 400+ connections | |
| Geographic Coverage | 100 countries across North America, Europe, Asia-Pacific, Latin America |
Pricing & Fee Structure
Fee structure and pricing model
Pricing & Fee Structure
Custom pricing model
Custom (instance + per-tx)
Custom (PSP-dependent)
Depends
400+ payment methods and anti-fraud providers via single integration
Depends on PSP
Depends on PSP
Custom
Custom
No
Pricing Details
Custom pricing model. Predictable monthly instance cost plus a small per-transaction fee. No flat percentage. No published numbers. The instance cost scales with infrastructure footprint — a single-region deployment is cheaper than a multi-region active-active deployment. The per-transaction fee is described as 'small' versus the 0.2-0.7% orchestration fees of Primer and Corefy. Gr4vy's pitch is that at high transaction volume the fixed instance cost outperforms percentage pricing. The trade-off is that there is no entry-level published price you can compare without a sales call, and the fixed instance cost is overhead at smaller volumes. PSP processing costs are separate — those come from whichever acquirers you connect (Adyen, Checkout.com, Stripe, etc.). The all-in cost is PSP rate + Gr4vy infrastructure + Gr4vy per-tx fee.
Negotiation Tips
Run the math at your projected enterprise volume before signing. At 10 million transactions a month, a 0.3% routing fee on a $50 average ticket is $1.5M annually. A fixed $X monthly instance plus a fraction of a cent per transaction could be a fraction of that — or could be more if the instance cost is high. The only way to know is to get a written quote, ideally side-by-side with Primer and Corefy quotes for the same projected volume. For Australian, European or APAC merchants whose pricing should also factor in regional data residency, that is a Gr4vy strength that competitors cannot match at price parity. Negotiate for transparent reporting on per-PSP routing performance so you can prove the orchestration layer is recovering more revenue than it costs.
Speed & Settlement
Transaction processing and settlement timelines
N/A
Player-initiatedN/A
Operator payoutDepends
To operator accountMulti-currency (via PSPs)
Settlement optionsTransaction speed is determined by the connected PSP, not Gr4vy. Gr4vy adds minimal routing latency on top of the underlying processor. Settlement, deposit speed and withdrawal speed all depend on whichever acquirer processes the transaction. The routing value comes from automatic failover: if one PSP slows down or starts declining, traffic redirects to a healthier connection in real time. Integration takes 1-3 weeks for the orchestration layer itself, faster if your engineering team already has experience with payment APIs. The Ding case study cites 3 days to integrate a new gateway through Gr4vy versus 3-6 weeks for a direct PSP integration. Onboarding (KYB, instance provisioning, PSP credential collection) adds 2-4 weeks before the first live transaction. Faster than IXOPAY's 2-4 week integration window, comparable to Corefy's 1-3 weeks, slower than Primer and Finera at about 1 week. Updated Q2 2026.
Integration & Tech
Developer experience and technical capabilities
API Type
Single API + SDK
Onboarding
2-4 weeks
Sandbox
Full sandbox environment provisioned per merchant
Mobile SDK
Swift SDK for iOS, Kotlin SDK for Android. Server SDKs: TypeScript, Node (deprecated), Go.
White-Label
No
Docs Quality
Excellent
1-3 weeks
Integration Assessment
Single universal REST API plus SDKs in TypeScript (@gr4vy/sdk on npm, current), Go, Swift (iOS) and Kotlin (Android). The legacy gr4vy-node SDK is deprecated in favor of gr4vy-typescript. Hosted checkout (Embed), Secure Fields with native 3DS2, payment links and e-commerce plugins for commercetools, Magento and Salesforce Commerce Cloud. Sandbox is provisioned per merchant. Documentation rated Excellent. Per the Ding case study, integrating a new gateway through Gr4vy took 3 days versus 3-6 weeks via direct PSP integration. Note: the TypeScript SDK is in beta and Gr4vy advises pinning to a specific version to avoid breaking changes.
Risk & Compliance
Licensing, fraud prevention, and regulatory compliance
Compliance Context
PCI DSS Level 1 service provider certification. SOC 2 Type 2 certified — a meaningful step beyond the SOC 2 Type 1 some orchestrators stop at. GDPR and CCPA compliant. Australian Privacy Law standards supported. The single-tenant architecture is a security feature in itself: your tokens, transactions and PII are not on shared infrastructure. BYOK (bring your own key) supports merchants with strict key-management policies. Sardine integration adds fraud and AML signals at the orchestration layer. Riskified integration available for merchants who want ML-based approve/decline decisions. Native 3DS2 in Secure Fields supports frictionless flows, browser fingerprinting and step-up challenges without redirecting customers off-domain.
About Gr4vy: Company Background
Company and product information
Company History
Founded in 2020 in San Mateo, California by John Lunn, Ali Minaei and Cristiano Betta. Lunn joined PayPal as employee number four in the UK in 2006, built PayPal's developer relations team and was instrumental in the 2013 Braintree acquisition. After leaving PayPal he started Gr4vy with the thesis that payment orchestration should be cloud-native and single-tenant rather than retrofitted multi-tenant SaaS. The first Series A closed in April 2021 at $11.1M led by Nyca Partners.
Series A extension of $15M closed January 2022 led by March Capital, putting Gr4vy at a $115M post-money valuation and total funding around $27.2M across seven investors. The company stayed small and focused — by 2023-2024 it was running with roughly 50 people, well below the 200+ at Primer despite similar product scope. The product roadmap added Vault for tokenization, Sardine for fraud, Mastercard Click to Pay support and BYOK key management. PCI DSS Level 1 and SOC 2 Type 2 certifications landed in this window.
Today: ~57 employees, distributed across the US, UK, EU and APAC. Marquee 2025 client wins include Trek Bicycles (March 2025), Grammarly (June 2025) and Wpay/Woolworths Group powering Australia's largest grocery retailer. Q2 2025 product update added native 3DS in Secure Fields and agentic-payments support for AI commerce. 400+ connected payment methods and anti-fraud providers. No Trustpilot profile, 5/5 from 1 review on G2, ~4.5/5 from 4 reviews on Glassdoor. Updated Q2 2026.
What Users Say: Trustpilot & Review Analysis
Our analysis of 0 reviews from Trustpilot and industry sources
Trustpilot Presence
No Trustpilot profile. Gr4vy is a B2B-only orchestration platform — end users never see it directly, so consumer review sites are not the right signal. Treat the client list and case studies as the primary reputation evidence instead.
Notable Clients
Trek, Grammarly, Wikimedia Foundation, JustGiving, Zip, BitPay, Wpay (Woolworths Group), Ding, ELEVEN Sports, FuturHealth, PlayHQ, Baby Bunting, Mattilda, Setplex
Enterprise non-gambling customers across multiple verticals. Trek (global cycling retail, unifying e-commerce and 1,000+ physical stores), Grammarly (writing SaaS), Wikimedia Foundation, JustGiving (charity), Zip (BNPL), BitPay (crypto). Wpay (Woolworths Group, Australia's largest grocery retailer). Ding (mobile top-up across 140+ countries, gateway integration cut from 3-6 weeks to 3 days). ELEVEN Sports (OTT video streaming, not gambling). FuturHealth (healthcare). PlayHQ (grassroots sports administration, not betting). Baby Bunting (children's retail, 2.8% authorization uplift in published case study). No published online casino, sportsbook, poker or lottery client. The closest sports-adjacent customers are streaming and amateur-sports admin, neither of which is real-money gambling.
Operational Details
Business terms, contracts, and support
Founded by John Lunn (ex-PayPal/Braintree Global Director of Developer Relations), Ali Minaei, Cristiano Betta. $27.2M total funding: $11.1M Series A April 2021 led by Nyca Partners; $15M Series A extension January 2022 led by March Capital. Post-extension valuation ~$115M. Notable client wins in 2025: Trek (March 2025), Grammarly (June 2025), Wpay/Woolworths Group (powers their payments platform). FAQ explicitly lists unlicensed gaming as not supported.
Frequently Asked Questions
10 questions about Gr4vy
Not really. Gr4vy's FAQ explicitly lists unlicensed gaming among prohibited verticals, alongside adult content, firearms, tobacco and drugs. There are no public case studies with online casinos, sportsbooks, poker rooms or lotteries. There is no responsible gaming module, no MGA or UKGC partnership material, and no documentation aimed at gambling-compliance use cases. For licensed iGaming operators, look at Corefy, IXOPAY, Finera or direct iGaming PSPs like Nuvei, Paysafe and Solidgate instead.
Single-tenant cloud architecture. Every Gr4vy customer gets a dedicated Google Cloud instance with their own data, isolated infrastructure and a configurable region for sovereignty rules. Primer, Corefy and IXOPAY all run multi-tenant SaaS. That isolation costs more and provisions slower, but for security-conscious enterprises and operators in jurisdictions with strict data residency laws (Australian APP, EU GDPR, sovereign-cloud requirements in Indonesia or Saudi Arabia), it is a real differentiator. The single-tenant model also avoids noisy-neighbor latency and reduces the blast radius of a tenant-level security incident.
No. Gr4vy is a pure orchestration layer. You bring contracts with PSPs (Adyen, Checkout.com, Stripe, Worldpay, etc.) and Gr4vy routes between them through one API. Same model as Primer, Corefy and IXOPAY. If you want processing and routing in one provider, look at Nuvei, Adyen or Checkout.com with their built-in smart-routing features.
Custom. No public pricing. The model is a predictable monthly instance cost plus a small per-transaction fee — not the 0.2-0.7% percentage fee that Primer and Corefy use. At enterprise volume the fixed cost can come out cheaper than a flat percentage. At smaller volumes the fixed instance cost is overhead. The only way to know what you would actually pay is a sales call. PSP processing costs are separate.
Total funding $27.2M across seven investors. Series A of $11.1M closed April 2021 led by Nyca Partners. Series A extension of $15M closed January 2022 led by March Capital, putting the post-money valuation at about $115M. The company stayed deliberately small — roughly 57 employees as of 2026. That is much smaller than Primer at 220+. Smaller team, less capital raised, more focused product. Counterparty risk exists but the marquee 2025 client wins (Trek, Grammarly, Woolworths) and the enterprise sales model suggest stable revenue. No 2024-2025 funding round is publicly announced.
400+ payment methods and anti-fraud providers through one universal API. Cards (Visa, Mastercard, Amex, JCB, Discover and local schemes), digital wallets (Apple Pay, Google Pay, PayPal), BNPL (Affirm, Afterpay, Klarna via PSPs), bank transfers (SEPA, ACH, iDEAL, PIX, Trustly), gift cards, prepaid and crypto via BitPay and other connected providers. Mastercard Click to Pay added through a 2025 partnership. The 400+ number is total ecosystem connections — what is enabled for your operation depends on which connections sales configures.
PCI DSS Level 1 service provider, SOC 2 Type 2, GDPR-compliant, CCPA-compliant, Australian Privacy Law standards supported. SOC 2 Type 2 is a meaningful step beyond Type 1 — it certifies operating effectiveness of controls over time, not just design. No acquiring license, no banking license, no gambling license — those sit with connected PSPs.
Trek (cycling retail, signed March 2025), Grammarly (writing SaaS, signed June 2025), Wpay/Woolworths Group (powers Australia's largest grocery retailer's payments platform), Wikimedia Foundation, JustGiving, Zip, BitPay, Ding (mobile top-up across 140+ countries), ELEVEN Sports (OTT streaming), Baby Bunting, FuturHealth, PlayHQ, Mattilda and Setplex. The Baby Bunting case study cites a 2.8% authorization uplift. The Ding case study cites 3 days to integrate a new gateway versus 3-6 weeks. No real-money gambling client is on the list.
1-3 weeks for the orchestration layer integration itself, faster if your engineering team is already comfortable with payment APIs. Onboarding (KYB, instance provisioning, PSP credential collection) adds 2-4 weeks before the first live transaction. The Ding case study cites 3 days to integrate a new gateway through Gr4vy once the platform is live. SDKs available in TypeScript, Go, Swift and Kotlin. E-commerce plugins for commercetools, Magento and Salesforce Commerce Cloud.
Because Gr4vy comes up in payment-orchestrator shortlists and it is worth confirming what the platform is not. It is well-engineered, well-funded enough, and has real enterprise customers — but it is not built for online gambling and the vendor itself excludes unlicensed gaming. Reading this review saves an iGaming operator a sales call. If you process gambling traffic, the orchestrators built for it are Corefy, IXOPAY, Finera. The PSPs built for it are Nuvei, Paysafe, Solidgate, EMerchantPay.
Our Verdict: Should You Use Gr4vy?
Final assessment for iGaming operators
Overall iGaming Score
Summary
Gr4vy is a well-engineered, deliberately small enterprise payment orchestrator built on single-tenant Google Cloud infrastructure rather than multi-tenant SaaS. The architectural choice is genuinely differentiated and lands well with security-conscious enterprises and merchants in jurisdictions with strict data-residency rules. PCI DSS Level 1, SOC 2 Type 2, 400+ connected methods, real marquee clients (Trek, Grammarly, Woolworths, Wikimedia). The honest read for this site's audience: Gr4vy is not built for iGaming. The FAQ excludes unlicensed gaming, there are no published gambling case studies, no responsible gaming module, no MGA or UKGC partnerships. For licensed iGaming operators this is the wrong tool. For enterprise non-gambling merchants with $1M+ monthly volume and a security or sovereignty driver, Gr4vy is one of the better orchestrators on the market.
Strongest Point
Single-tenant cloud architecture. Gr4vy is the only orchestrator in this database that gives every merchant a dedicated Google Cloud instance rather than a tenant on shared infrastructure. That solves three real problems: data residency in regions with strict sovereignty rules, security blast-radius isolation from other customers, and noisy-neighbor latency in multi-tenant SaaS. SOC 2 Type 2 plus PCI DSS Level 1 on top of single-tenant isolation makes Gr4vy a stronger compliance story than Primer, Corefy or IXOPAY for security-sensitive non-gambling enterprises.
Key Limitation
No iGaming track record at all. This is not a 'limited' iGaming portfolio like Primer has with Dabble and Jackpot.com — it is zero. The vendor's own FAQ excludes unlicensed gaming, and there is no public material indicating support for licensed gambling either. There is no responsible gaming tooling, no chargeback management language aimed at the high chargeback environment of betting, no MGA or UKGC partnership. For online casinos, sportsbooks, poker rooms or lotteries this is a non-starter regardless of how good the underlying engineering is. The secondary limitation is company size — 57 people running enterprise infrastructure for Trek, Grammarly and Woolworths is impressive but creates counterparty risk if a critical engineer leaves or a major customer demands an SLA the team cannot support.
Recommendation
Choose Gr4vy if you are an enterprise non-gambling merchant — e-commerce, retail, OTT streaming, edtech, healthcare, nonprofit, crypto — with $1M+ monthly volume, a real data-residency or single-tenant-security driver, and a budget that can absorb enterprise pricing. The Trek, Grammarly and Woolworths case studies suggest the platform works at that scale. If you operate any flavor of online gambling, do not bother with Gr4vy: the FAQ disqualifies you, the case studies do not include you and the team has not built tooling for you. Choose Corefy or IXOPAY for white-label iGaming orchestration with 500-600+ connectors. Choose Finera for iGaming-focused orchestration with the lowest minimums. Choose Nuvei, Paysafe or Solidgate for direct iGaming acquiring with built-in routing. Updated May 2026.
Pros
- Single-tenant Google Cloud architecture. Every merchant gets a dedicated instance with their own data, isolated infrastructure and configurable region for sovereignty rules. No other orchestrator in this database does this. Genuine differentiator for security and data-residency-conscious enterprises.
- SOC 2 Type 2 plus PCI DSS Level 1. Most orchestrators stop at PCI DSS Level 1. SOC 2 Type 2 certifies operating effectiveness of controls over time, not just design. Stronger compliance story than Primer, Corefy and IXOPAY for security-sensitive non-gambling customers.
- 400+ connected payment methods and anti-fraud providers through one universal API. Cards, wallets, BNPL, bank transfers, crypto via BitPay and others. Mastercard Click to Pay support added in 2025.
- Marquee enterprise client wins. Trek (March 2025), Grammarly (June 2025), Wpay/Woolworths Group powering Australia's largest grocery retailer's payments platform, plus Wikimedia, JustGiving, Ding and ELEVEN Sports. Customers willing to put a routing layer in front of their entire payments stack on a 57-person vendor signal trust.
- Founder credibility. John Lunn was PayPal's fourth UK employee and built PayPal's developer relations team, then helped acquire Braintree in 2013. He knows what large-scale payments infrastructure should look like and built Gr4vy to address gaps he saw at PayPal.
- Predictable infrastructure-plus-per-transaction pricing. At enterprise volume the fixed monthly instance cost plus a small per-tx fee can come out cheaper than the 0.2-0.7% routing fees of Primer and Corefy. Pricing scales more linearly than flat percentages.
Cons
- Excludes online gambling. Gr4vy's own FAQ lists unlicensed gaming in prohibited verticals. No published case study with any online casino, sportsbook, poker room or lottery. No responsible gaming tooling, no MGA or UKGC partnership material. For the audience of this site, this is disqualifying.
- No public pricing. Sales-led, custom-quoted. The pitch is that the model is cheaper than percentage-based routing at scale — but you cannot validate that without a sales call and a written quote. Compare to Corefy and Primer who at least publish ballpark ranges.
- Small company. 57 employees running enterprise payment infrastructure for Trek, Grammarly and Woolworths. Impressive operationally, but creates counterparty risk if a critical engineer leaves or a major customer's SLA demand exceeds team capacity. Compare to Primer at 220+ employees and Adyen at 4,000+.
- Funding stale. Last public funding round was the $15M Series A extension in January 2022. No publicly announced 2023, 2024 or 2025 round. Either the company is now revenue-stable enough to self-fund or it is heading toward another raise; either way, no fresh investor signal in three years.
- TypeScript SDK is in beta. Gr4vy advises pinning to a specific version to avoid breaking changes. The legacy gr4vy-node SDK is deprecated. For an enterprise infrastructure product, this is a small but noticeable signal that the developer ecosystem is still maturing.
- Orchestrator-only. You bring your own PSP contracts. Gr4vy does not handle acquiring, banking, KYC or chargeback liability — those all sit with the connected processors. For operators who want one provider doing everything, look at Adyen, Checkout.com or Nuvei instead.
Ready to evaluate Gr4vy for your business?
Gr4vy vs. Alternatives: How It Compares
Similar payment processing solutions
For iGaming-focused orchestration, Corefy and IXOPAY are built for high-risk gambling traffic with 500-600+ connectors and explicit MGA/UKGC support. Finera offers iGaming-focused orchestration with the lowest minimums in the category. For direct iGaming acquiring without an orchestration layer, Nuvei, Paysafe and Solidgate handle real-money gambling natively with built-in routing. For enterprise non-gambling merchants who want orchestration without the single-tenant cost, Primer offers a visual flow builder at lower minimums.
When to Choose an Alternative
Choose Corefy for licensed iGaming orchestration with 600+ connectors, $250k minimum, AI risk scoring and the strongest published Trustpilot among orchestrators at 4.2/5. Built for gambling and high-risk verticals that Gr4vy explicitly excludes.
Choose IXOPAY for enterprise white-label iGaming orchestration with SoftSwiss and EveryMatrix pre-built adapters, PCI DSS Level 1 Service Provider status and TokenEx tokenization. Higher barriers ($1M+ minimum, $5k+ setup, 12-month contract) but built for the iGaming use case Gr4vy ignores.
Choose Finera for iGaming-focused orchestration with $300k minimum, 0.1-0.5% routing fees and no lock-in. Lower barriers than Gr4vy, explicit gambling positioning, smaller-than-enterprise operators can actually sign up.
Choose Primer if you want orchestration with a visual drag-and-drop flow builder for non-engineering teams and at least one published sports-betting case study (Dabble). Multi-tenant SaaS instead of Gr4vy's single-tenant infrastructure, but lower barriers and a real iGaming reference.
Skip orchestration entirely. Nuvei handles direct iGaming acquiring with 720+ methods, MGA/UKGC support and built-in smart routing. One provider instead of orchestrator-plus-PSPs, with the iGaming case studies Gr4vy lacks.
Choose Paysafe for direct iGaming acquiring with the strongest US sportsbook reference list (DraftKings, FanDuel, BetMGM) and explicit gambling licensing. No orchestration layer needed.
Primer
Payment OrchestratorCorefy
Payment OrchestratorIXOPAY
Payment OrchestratorFinera
Payment OrchestratorEnd of Report. Gr4vy Provider Assessment Report 2026
Prepared and reviewed by the iGaming Payment Solutions Editorial Team · May 13, 2026