> 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/three-pillars-of-credibles-payment-stack.md).

# Three Pillars of Credible’s Payment Stack

### **PayFi Credit — Financing**

A short-term (1–7 day) receivable-backed financing layer that advances liquidity at the moment of settlement. This layer bankrolls payment flows themselves—without underwriting merchants or consumers.

### **Payment Orchestration — Execution**

A unified gateway and aggregator layer that routes pay-ins and pay-outs across:

* Local payment methods
* Banking partners
* Stablecoin rails

This orchestration optimizes for speed, cost, FX efficiency, and compliance—abstracting away fragmented local infrastructure.

### **Settlement Queues — Liquidity**

A structured settlement system where fiat clearing completes asynchronously in the background, while end users and merchants receive funds instantly. Liquidity is allocated, repriced, and recycled based on real payment flow demand.


---

# 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/three-pillars-of-credibles-payment-stack.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.