Credible Finance: T+0 settlement for the businesses card gateways decline

Every card payment hides a three-day loan. The customer pays instantly, the acquirer settles the merchant at T+3, and someone — usually the merchant's cash flow — eats the float. Credible Finance turns that float into product: merchants get paid T+0 from stablecoin liquidity pools, the pools get repaid when the acquirer settles, and LPs earn yield for financing the gap. Layer on multi-PSP orchestration and local rails (UPI, Pix, SEPA, ACH, and more), and you get an open payments stack aimed at the businesses traditional gateways quietly decline.

The company claims $700M+ processed across 42+ markets, 37+ currencies, and 86+ payment methods, with backers including Colosseum, Circle, Polygon, Outlier Ventures, 0G Labs, Superteam, and the Stellar Community Fund. The regulated US entity is Kiwimoney Inc, a FinCEN-registered MSB, operating through locally licensed partners elsewhere. And as of July 13, 2026, the $CRED ownership token raise is live on MetaDAO.

Click to zoom

From India remittance hack to payments orchestrator

Credible placed near the top of the Solana Cypherpunk Hackathon with stablecoin remittance rails into India, then joined Colosseum accelerator cohort 4 (~0.67% acceptance, $250K investment). The product widened from remittance into full orchestration: pay-in routing, AI risk underwriting, instant merchant settlement, global payouts, and permissionless prefunding pools.

Positioning is explicit on the homepage: "the payments rail for businesses traditional gateways won't touch." Eight verticals get their own industry pages — prediction markets, stablecoin fintechs, creator platforms, web3, traders and brokers, AI startups, gaming and sports (skill-based; they say they do not serve betting/wagering/gambling apps), and entertainment. The common thread is velocity, chargeback risk, and multi-jurisdiction user bases that legacy PSPs never modelled for.

How T+0 settlement actually works

Click to zoom

Clearing and settlement are decoupled. The merchant does not pre-fund; the pool advances capital the moment RiskAI underwrites the receivable. When the acquirer finally settles, the pool is repaid. That is the same economic job a merchant cash-advance desk does at a bank — packaged as an on-chain (or chain-settled) liquidity product with programmatic repayment.

Solana (and Polygon) show up as settlement rails for the advance and the pool, where stablecoin transfers are fast and cheap enough that "pay the merchant now" costs cents, not wire fees. The Credible Foundation frames this as a three-layer open stack:

Click to zoom

The honest flip side: ~16% APY is not risk-free yield. LPs underwrite acquirer settlement risk, merchant chargebacks, and Credible's risk models. Size positions like private credit, not like a money market.

Product surface for builders

For a fintech or merchant platform, Credible is one API in front of many rails — collections, global payouts, virtual collection accounts, ledger/webhooks, prefunding pools, and per-transaction risk underwriting.

Click to zoom

Onboarding is self-serve by design: create a partner account at partner.credible.finance, complete async KYB, then hit payments, payouts, and ledger endpoints. White-glove is available for high volume or bespoke risk models; you do not need a sales call to read the docs. Virtual collection accounts follow the same pattern covered in bank APIs for Solana apps.

Developer docs and API auth

Official docs live at docs.credible.finance. Public metadata describes the surface as authentication, webhooks, KYC/KYB onboarding, payouts, and collections. Note: the docs site is session-gated (Next.js auth gate) — you create an account and complete onboarding before the full guide tree is useful. That is a friction point for pure research; it is also normal for a regulated MSB shipping live money movement.

What is public without a login is the HMAC request-signing pattern in github.com/crediblefinance/sdk-examples. Every request carries an API key, a millisecond nonce, a receive window, and an HMAC-SHA256 signature over a sorted JSON payload:

Click to zoom

// From crediblefinance/sdk-examples (simplified)
const headers = {
  "X-API-KEY": apiKey,
  "X-NONCE": Date.now(),
  "X-RECV-WINDOW": 5 * 1000,
}
const message = sortObjectKeys({
  ...bodyOrParams,
  "X-NONCE": headers["X-NONCE"],
  "X-RECV-WINDOW": headers["X-RECV-WINDOW"],
})
headers["X-SIGNATURE"] = CryptoJS.HmacSHA256(
  JSON.stringify(message),
  secretKey,
).toString()

That is exchange-style request authentication (Binance/Bybit lineage), not a simple Bearer token. Clock skew and key-sorting bugs will fail requests; implement the sort-and-string rules exactly as in the sample. Idempotency and webhook verification details sit behind the authenticated docs.

Public GitHub under github.com/crediblefinance is still thin: sdk-examples (the auth scripts above), a brand kit, and switch — a fork of Juspay's Hyperswitch, the open-source Rust payments switch. Building on Hyperswitch is a reasonable engineering choice; read "our open-source switch" with that context.

Where it sits in the landscape

Bridge, Sphere, and Squads Grid (see bank APIs) sell you rails — virtual accounts, on/off-ramps, compliance. Stables.money sells a multi-chain stablecoin payments API. Credible sells orchestration + instant settlement financing on top of rails, with an explicit focus on verticals those providers often restrict.

Click to zoom

Complementary, not a drop-in for the same RFP — unless your bottleneck is "Stripe / Adyen declined us" or "we need T+0 without prefunding our own float." The Foundation's comparison table is self-authored marketing; verify against each provider. For Solana builders, the interesting primitive is still the pool-as-working-capital design — DeFi yield that is literally financing real card receivables.

$CRED and the MetaDAO raise

$CRED is described as the ownership and coordination token for Credible Foundation: on-chain governance (upgrades, fees, treasury), revenue share from settlement and orchestration, and a native unit across Credible / Creddy / partner fintechs. Launch mechanism is MetaDAO futarchy— market-governed treasury after the raise, not a one-off snapshot vote.

The curated raise opened July 13, 2026 for a four-day USDC commitment window on metadao.fi/projects/credible/fundraise. Per the team's own corrections on X: they are raising $2–4M at a $9M FDV cap; token price is set by the raise mechanics (not a fixed $0.20 sticker you may see on third-party ICO aggregators); ICO participants unlock 100% at TGE, while existing investors and team have longer cliffs plus performance-based unlocks. MetaDAO's usual pattern: if commitments exceed the cap, pro-rata refunds; if the minimum is missed, capital returns; proceeds land in a Squads multisig under futarchy governance.

This article is not investment advice. Treat token terms, FDV, and unlock schedules as moving parts — verify on MetaDAO and primary Credible sources before committing capital.

Resources

• Product: credible.finance · partner onboarding partner.credible.finance · LP pool app app.credible.finance
• Docs: docs.credible.finance (auth, webhooks, KYC/KYB, payouts, collections — account required)
• Foundation / stack / $CRED: credible.foundation · token page
• Raise: MetaDAO curated raise
• GitHub: github.com/crediblefinance — sdk-examples for HMAC auth; switch is the Hyperswitch fork
• X: @crediblefin

TL;DR

• Credible = payments orchestration for risk-aware verticals, with T+0 merchant settlement financed by stablecoin pools while acquirers clear T+3 in the background.
• Self-serve path for builders: KYB → HMAC-signed REST API → collections, payouts, ledger, webhooks. Docs are real but session-gated.
• Colosseum cohort DNA, $700M+ claimed volume, Circle/Polygon on the backer list; $CRED is live on MetaDAO as of mid-July 2026.
• 16% pool APY is private credit. Public GitHub is thin. Good product story — read the risk and the docs before you wire production volume or LP capital.