Request Finance

the eor / contractor pay space rough shape: \- deel, remote, oyster, papaya global, multiplier, ontop, rippling. these are the big eor names. varying degrees of stablecoin-payout offering, some very real, some pilot, some still on the roadmap. \- request finance, bitwage, toku. crypto-native contractor pay, less full eor more pure payout. \- platforms like trolley (formerly payment rails), tipalti, papaya. payout-platform shape, used underneath some eors. the architectural distinction worth keeping in mind: the eor handles employment and tax obligations, the payout layer handles money movement. some companies bundle both under one brand, most use infra underneath. when youre evaluating its worth knowing which layer the vendor sits in.

the stablecoin pressure is real and it's only going in one direction. Deel and Papaya Global have gotten better for the Nigeria and Indonesia corridors specifically and handle the compliance layer which is the scary part you mentioned. Airwallex is worth looking at too for volume, better rates than Wise at scale and more corridors. the AML concern with stablecoins is legitimate but there are now proper B2B rails built on USDC with built in compliance, Bridge and Request Finance are two worth looking at if you want to go that direction without rolling your own.

I've been seeing Notabene Flow pop up everywhere lately in fintech Twitter and some VASP compliance groups. Notabene's the company behind that massive Travel Rule network handling over $1T in volume yearly, and they launched Flow in late 2025 as their stablecoin payments play. From what I've dug into on their site (notabene.id/flow) and some coverage in CoinDesk and BusinessWire, it seems like a solid B2B platform for stablecoin stuff. Key bits: open network that's protocol-agnostic (not locked to one issuer like some competitors), pull payments which is huge for direct-debit style on crypto rails, recurring subscriptions, invoicing and billing, instant settlement across 2,000+ regulated entities, and built-in FATF Travel Rule compliance so no extra AML bolt-ons. They have partners like Bitso, Flutterwave, Monerium, and Zodia Custody already on board. Solves real pains like cross-border B2B transfers faster/cheaper than SWIFT for $100K+ moves, or treasury teams skipping pre-funded accounts. Pricing isn't public, but it looks enterprise-tier, probably volume-based with a shared-revenue model for network partners. I'm running payments for a mid-sized cross-border fintech, and we're eyeing it to handle recurring stablecoin billing and multi-party flows without stitching together wallets and compliance vendors. I'm leaning toward giving it a shot, but is Notabene Flow pricing actually worth it for volumes under $10M/month? A few questions for folks who know: 1. What's the real pricing structure? Any setup fees, per-tx costs, or minimums? How does the shared-revenue thing work in practice? 2. ROI-wise, has it paid off for B2B or fintech teams? Like, time saved on compliance/invoicing vs cost? 3. For pull payments and recurring subs, does it deliver on instant settlement without hiccups, especially vs manual wallet flows? 4. Any gotchas with integrations for wallets/PSPs, or comparisons to stuff like Request Finance for invoicing? Looking forward to hearing real experiences before we commit.

A few months back, I was running a cross-border B2B SaaS platform serving clients in Africa and LatAm. We wanted to bill our enterprise customers in stablecoins for monthly subscriptions, but everything was manual. Customers had to push USDC or EURC from their wallets every month, which meant constant reminders, failed payments, and disputes. No way to automate pulls like ACH or SEPA. Tried cobbling together some wallet APIs with Request Finance for invoicing, but compliance was a nightmare, no Travel Rule handling, and settlement took days. Heard about Notabene Flow right after their September 2025 launch. They're the Travel Rule compliance pros with that massive 2,000+ VASP network handling over $1T yearly, so I figured their new stablecoin payments layer might actually work for B2B recurring stuff. Signed up for their enterprise tier (volume-based pricing, shared revenue with partners), integrated via API in about a week. Super straightforward since it's protocol-agnostic, works with USDC, EURC, you name it. Here's my exact workflow now for recurring stablecoin subscriptions: 1. Customer onboarding: Send an invoice via Notabene Flow's billing tool. They approve once, link their wallet/custody (we use Dfns and Zodia integration), and set up authorization for pulls. 2. Recurring setup: Define the schedule (monthly, quarterly), amount in stablecoins, and any FX handling. Flow handles the pull payment equivalent, no pre-funding needed. 3. Execution: On due date, Flow routes via their open network. Instant settlement across regulated VASPs, with built-in FATF Travel Rule data sharing. Disputes? Built-in resolution flow. 4. Reconciliation: Dashboard shows everything, treasury auto-updates, and we get notifications for any holds. Processed $250K in subscriptions last month alone, zero failed payments, cut our ops time from 10 hours/week to 30 minutes. Costs are way below SWIFT wires (no correspondent fees), and compliance team's happy, no more bolt-on AML vendors. Multi-party flows let us add intermediaries like Yellow Card for local ramps without headaches. If you're doing B2B stablecoin billing, Notabene Flow nails the recurring subscription gap that wallets can't touch. Previously stuck with push-only hacks, now it's set-it-and-forget-it. Anyone else running similar workflows? What's your setup?

I’m looking at USDC invoicing for freelancers/contractors and trying to understand the real workflow pain. If you receive client payments in USDC, how do you handle: 1. Matching wallet transactions to invoices 2. Sending a receipt/proof of payment 3. Recording USD value at receipt time 4. Exporting clean records for QuickBooks/accountant/taxes 5. Preventing wrong-chain/wrong-token mistakes Are people using Request Finance, Coinbase Business, StableInvoicing, spreadsheets, wallet screenshots, or something else? I’m considering building a small tool around this, but only if this is still annoying/manual. If you’ve solved it cleanly, what’s your setup?

Disclosure: I work on an off-ramp product (Madhouse Wallet) so take that context when reading. Wanted to open a thread on a specific problem this sub rarely discusses: DAO and DeFi team treasury management for the boring part — paying actual humans. The setup everyone has: \- Treasury is in USDC on some mix of Ethereum, Arbitrum, Base, maybe Polygon \- Contributors are in 12 countries \- Every month the ops person has to send everyone their salary in fiat \- Currently most teams I know do one of: (a) send USDC to each contributor, contributor deals with off-ramp, (b) use Request Finance or similar, or (c) the ops person has a Binance account and manually off-ramps then wires The problems with each: \- Option A pushes the cost onto the contributor. Contributor in Kenya pays 2-3% to off-ramp, contributor in Germany pays 0.5%. Feels unfair. \- Option B works but only covers a subset of corridors well. Weak on emerging markets. \- Option C does not scale past 5 people and has compliance risk. What would actually solve this at the DAO level: a programmable payout API where you post a CSV of (address or bank detail, amount, currency) and USDC gets debited from the treasury, each contributor gets paid in their preferred local rail. We built toward that problem but I am curious — for people running treasury at a DAO, does this framing match your reality, or is the bigger pain somewhere else (governance around payroll, on-chain reporting, tax)?

native usdc integrations with hubspot are still pretty limited, so most teams end up using middleware like zapier, make, or webhooks from crypto payment processors instead of stripe. tools like coinbase commerce, circle, or request finance can trigger payment events that you push into hubspot deals or workflows without the double fee problem. it’s still a bit custom, but using webhook-based updates into hubspot is usually the cleanest and most flexible approach.

It's important. I was just looking at the new OrvexPay. "Next-generation crypto payment infrastructure built for modern businesses and developers." They have a lot of SDKs on GH: https://github.com/orvexpay Compared to say https://request.network/ from France - a seemingly similar service, but much older. https://github.com/RequestNetwork I wonder how much of OrvexPay has been vibecoded? Kind of mysterious. Are their front-page stats legit? https://orvexpay.com/ $2.4B+ Processed Volume | 12k+ Active Merchants It's like vibecoding allows for much shorter and simpler runways for startups to IPO, especially considering the Kraken/Nasdaq deal. https://www.coindesk.com/business/2026/03/09/nasdaq-and-kraken-are-teaming-up-to-let-you-trade-tokenized-stocks It also allows large systems to be built cheaply, quickly and simply, but will they scale? If you wanted to guard your IP, I would stay off GitHub. It's an AI training ground. Am I right?

The coordination layer angle is key. Request Network tried this early on — structured payment requests with metadata, chain/token preferences, and tracking. Challenge was always network effects: getting both sides to adopt. A simpler wedge might be crypto-native invoicing for freelancers — something that generates both a payment link and a fiat-denominated record for tax purposes. That solves a real pain point beyond UX.

Went through this about a year ago. Few things: The accounting side is absolutely the bottleneck. QuickBooks doesn't natively handle crypto, so you'll need something like Cryptio or Request Network to sync transactions. Spreadsheets work fine if you're doing <10 payments/month, but it gets tedious fast. Your CPA is right to flag it. Even stablecoins need cost basis tracking because the USD value at transfer time vs settlement can drift slightly. Document TX hashes, wallet addresses, timestamps, and fiat value at send time. The IRS treats every transfer as a taxable event. On the contractor side, make sure they actually want USDC. If they need to off-ramp to local currency, that adds friction and potentially eats into the savings from avoiding wire fees. Some countries have better fiat off-ramps than others. Also worth setting up a multi-sig (Gnosis Safe) for the company wallet. Treasury controls matter more when it's not personal funds. What's your monthly volume looking like? That determines whether the tooling investment is worth it.

Hey everyone! Just wanted to share that Request Network has added r/Tronix (Tron) blockchain support for payment requests and invoicing. **Key highlights:** * Create payment requests for USDT (TRC-20) * Ultra-low fees (basically pennies) * Fast transaction settlement * Easy API integration for developers * Automatic payment detection This is perfect for anyone doing high-volume USDT transfers or looking for a much cheaper alternative to Ethereum mainnet. Tron now joins Ethereum, Polygon, Base, Arbitrum, and 10+ other supported networks. If you're building payment infrastructure or B2B invoicing tools, definitely worth checking out the [Request Network docs](https://docs.request.network).

Hey everyone! Just wanted to share that Request Network has added r/Tronix (Tron) blockchain support for payment requests and invoicing. **Key highlights:** * Create payment requests for USDT (TRC-20) * Ultra-low fees (basically pennies) * Fast transaction settlement * Easy API integration for developers * Automatic payment detection This is perfect for anyone doing high-volume USDT transfers or looking for a much cheaper alternative to Ethereum mainnet. Tron now joins Ethereum, Polygon, Base, Arbitrum, and 10+ other supported networks. If you're building payment infrastructure or B2B invoicing tools, definitely worth checking out the [Request Network docs](https://docs.request.network).

Privacy has been one of the biggest conversations in crypto lately, and Aleo just shipped Shield Wallet, a self-custodial wallet where balances, transaction amounts, sender/receiver details, and even gas fees are encrypted by default using zero-knowledge proofs. The idea is simple: you can hold, trade, buy, and send crypto without broadcasting your activity to the world. No one sees your balance, no one sees who you're transacting with, and no one sees how much you moved. It's not an opt-in privacy toggle. It's the default state. It's built on Aleo's L1, which was purpose-built for privacy from the ground up. They considered building on top of Ethereum initially but ultimately went the L1 route because bolting privacy onto an existing transparent chain has fundamental limitations. This matters beyond "privacy good." The people are comparing this wallet to is to Zcash's Zashi wallet moment: a native privacy wallet that makes the chain actually usable for everyday users. However, Aleo differentiates in the compliance angle. Unlike Tornado Cash, Aleo's architecture allows users to selectively disclose information to trusted parties (regulators, auditors, etc.) when needed. Privacy and compliance coexisting is a big deal for institutional adoption. Shield already has partnership that allow it to have traction from day one. They've already launched with integrations across stablecoin issuers (Circle xReserve, Paxos), on/off ramps (Banxa), bridges and swaps (HoudiniSwap, Hyperlane, Near Intents), and risk/analytics (TRM Labs). The staking side has validators like Figment, Everstake, and HashKey Cloud. Aleo itself has broader partnerships with Revolut, Request Finance, Global Dollar Network, and recently appeared on Binance Alpha. Aleo raised $250M+ from a16z Crypto, SoftBank, Tiger Global, Samsung Next, Polychain, and Coinbase among others. The team includes people from DOJ, the White House NSC, Google, Meta, Circle, and Paxos. I've been in the DeFi space for a while now, and the privacy narrative keeps getting louder for a reason: onchain transparency is a double-edged sword. Shield is the first real consumer-facing product from Aleo that makes their ZK tech tangible for regular users. The outcome remains to be seen, but it seems like the foundation they've laid is solid. You can get the wallet as a browser extension now. I'm happy to support brands like Aleo and share their work as I believe in the products they are creating.