> For the complete documentation index, see [llms.txt](https://credible.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://credible.gitbook.io/docs/primitives/evolution-of-credibles-modular-payfi-primitives.md).

# Evolution of Credible’s Modular PayFi Primitives

**Delayed Settlement → Instant Liquidity Advance**

**Primitive:** PayFi Advance\
Credible advances stablecoins or local fiat at the moment a payment is initiated, converting delayed settlement into instant liquidity.

> *Equivalent to moving from “wait-for-clearing” to “settle-now, clear-later”*

#### **Fragmented Gateways → Unified Orchestration**

**Primitive:** Payment Orchestration Layer\
Instead of relying on a single PSP (Stripe, PayPal), Credible dynamically routes transactions across multiple gateways, aggregators, and rails—maximizing uptime and speed.

> *Comparable to how routing protocols optimize network traffic*

#### **Trapped Capital → Yield-Bearing Settlement**

**Primitive:** Receivable-Backed Yield\
Settlement gaps (1–7 days) become yield-generating windows, where liquidity providers earn returns secured by in-flight payment receivables.

> *Settlement becomes a financial primitive, not a cost*

#### **Pre-Funding → Capital Efficiency**

**Primitive:** Liquidity Decoupling\
Merchants and neobanks no longer need to pre-fund accounts across countries. Capital is deployed only when payments occur.

> *Working capital is replaced by programmable liquidity*

#### **Batch Clearing → Real-Time Experience**

**Primitive:** Asynchronous Settlement Abstraction\
Fiat rails continue to clear on their own timelines—but users never experience the delay.

> *Settlement speed is fully decoupled from clearing speed*


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://credible.gitbook.io/docs/primitives/evolution-of-credibles-modular-payfi-primitives.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.