We have processed nearly $500M in cross-border payment volume in the seven months since Credible launched. That number understates the work; getting from idea to $500M of real settlement flow has involved more operational lessons, banking relationships, compliance choreography, and treasury choreography than we expected. We are sharing the inside view because we wish someone had shared it with us.
This is not a marketing piece. It is the operational journal of a payments infrastructure company growing through its first scale-up phase. If you are building or operating similar infrastructure, we hope it is useful.
The path to PMF
Credible was not always Credible. Our team spent ~18 months building tokenised RWA-backed lending and trade finance — a market we knew, a problem we cared about, and a regulatory perimeter we had operated inside before. We processed ~$50M in cumulative volume across those products and learned a great deal about underwriting on-chain.
What we kept hearing from operators was different from what we were building. They wanted instant payment settlement. They wanted local rails plus stablecoin float. They wanted cross-border at mid-market FX. They did not want another RWA primitive — they wanted infrastructure that solved their actual payment problem.
After winning Founders Villa in Q1 2025 and securing a grant from Circle in the same quarter, we redirected. The team's TradFi + Web3 experience translated directly: licensed banking partners, stablecoin custody, on/off-ramp operations, AML/CTF maturity. The shift to PayFi was a re-pointing of the same underlying capabilities. Within two quarters the new direction was producing more volume than the previous 18 months combined.
First customers: US remittance
Our first material payments customers were US-based remittance apps serving the diaspora corridors into India, the Philippines, Vietnam, and Nigeria. They had a specific problem: settling cross-border in seconds at mid-market FX, without holding NOSTRO accounts in each destination country.
We solved it with stablecoin float on the back-end and licensed local rail integrations on the front-end. The remittance app saw a single API; behind it we orchestrated USDC pools, licensed off-ramps, and per-corridor compliance. The customer's experience: same-day settlement at quoted FX, no surprises.
Within 90 days of first integration we were processing eight-figures of monthly volume per customer. Within 180 days the cumulative volume crossed $200M.
Operational lessons that surprised us
1. Settlement is harder than payments
Accepting money is the easy part. Disbursing it correctly, on time, to the right account, with the right tax and compliance metadata — that is where the engineering investment goes. Settlement-first design (reconciliation, tracking, dispute resolution, retry logic) is what separates infrastructure that scales from infrastructure that wobbles.
2. Banking relationships are the rate limiter
Every market we operate in requires a banking partner that understands what we do. Building those relationships — KYB, ongoing reporting, partner-bank risk reviews — is the slowest part of geographic expansion. We now treat the banking-partner sales cycle as a primary corporate priority, not as ops back-office work.
3. Compliance is a competitive moat, not a cost centre
Sanctions screening, transaction monitoring, KYC/KYB, suspicious-activity reporting, source-of-funds documentation — none of this is free, and none of it is glamorous. But customers we win away from competitors usually win because of our compliance posture, not despite it. Investing here is investing in customer acquisition.
4. Treasury operations need their own engineering team
Stablecoin pools, multi-chain custody, intraday rebalancing, FX hedging, partner-bank funding — at $400M+ in monthly flow this is a 5+ person engineering function with its own product roadmap. We learned to staff it sooner rather than later.
5. Customer support is part of the product
Payments customers do not call when things are working. When they call, they need answers about a specific transaction, in minutes, with full traceability. We staffed an internal support engineering team within the first 6 months. It is one of the highest-impact investments we made.
Banking and compliance: the harder yards
Every banking partner we onboard runs a multi-month KYB cycle — audited financials, beneficial ownership, AML programme review, sanctions screening capability, partner-bank reference checks. We invested early in producing an institutional-grade evidence pack and now run partner onboarding in weeks rather than months.
The same is true on the regulatory side. We are FinCEN-registered (MSB 31000324258161), and we are actively pursuing additional registrations and licences in line with our roadmap: Canadian RPAA, Singaporean MPI, Hong Kong MSO, US state MTLs, and EU/UK payments licences. Each licence is a multi-quarter exercise — but each one unlocks structural growth.
Scaling collections and payouts
At $400M+ in monthly flow we are processing tens of thousands of inbound and outbound payments per day across 40+ markets. The architecture that makes this work has four principles.
- Idempotent operations. Every API call carries an idempotency key; retries are safe.
- Provider abstraction. Each payment rail is wrapped in a uniform interface so we can hot-swap providers without product impact.
- Reconciliation-first design. Every flow has a planned reconciliation step before it is shipped.
- Live treasury observability. Every pool, every partner-bank balance, every NOSTRO/VOSTRO position is visible in real time, alerted on, and graphed.
What didn't work
We tried to build internal exchange/AMM capability for the FX leg in our first six months. We were wrong — partnering with specialist FX desks gave us better pricing, deeper liquidity, and faster iteration. We rebuilt the FX leg as a partner-orchestration layer, and the cost per transaction dropped 40%.
We also under-invested initially in dashboard and reporting for customers. Operators want their own visibility into volume, fees, settlement, and rejections. Building that out earlier would have shortened sales cycles.
The $5B target and beyond
Our 2026 target is $5B in annualised volume. Three things must go right. First, we must expand corridors — 20+ new markets and local rails in 2026, each requiring banking partners, regulatory engagement, and product integration. Second, we must scale the merchant gateway — moving up from remittance apps to merchant acceptance at internet scale. Third, we must launch Creddy — our consumer-facing payment method — and onboard the first cohort of consumer users.
None of this is hypothetical. We have built the architecture, the team, and the customer pipeline. The next 12 months are execution.
If you are building or buying payment infrastructure
Two takeaways. If you are building: invest in compliance, treasury observability, and partner-banking relationships from week one. The infrastructure you build around the payments is the part that scales. If you are buying: ask the vendor's leadership how they monitor pool exposure, partner-bank concentration, and per-corridor risk. The answers will tell you whether they are running infrastructure or running a demo.
We are happy to share more — talk to us if you are evaluating cross-border payments infrastructure for a serious business.