> 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/credible-overview/how-credible-works/pay-out.md).

# Pay-out

Credible enables neobanks, remittance fintechs, and global merchants to send money into emerging markets using a single payout integration, while delivering **T+0 settlement** through stablecoin-backed liquidity. Instead of managing prefunding, fragmented local rails, and delayed bank settlement cycles, customers can initiate payouts instantly and Credible orchestrates execution end-to-end.

<figure><img src="/files/WnlUJWFJowv4ccpU3YSK" alt=""><figcaption></figcaption></figure>

### Step 1: You Initiate a Pay-Out via One API

Your platform (neobank, fintech, or merchant) sends a payout request to Credible via API, including:

* beneficiary details (bank account / wallet / identifier)
* amount and currency
* purpose / metadata for reconciliation
* optional compliance fields (KYC/KYB references, source of funds, etc.)

Credible returns a payout intent and begins processing immediately.

### Step 2: Credible Validates Beneficiary + Applies Controls

Before funds move, Credible runs payout validations and controls such as:

* beneficiary verification (format, bank routing rules, wallet checks)
* compliance rules and corridor policies
* fraud / risk scoring and velocity limits
* KYB/KYC enforcement (as required per flow)

This reduces failure rates and prevents downstream reversals, retries, and settlement disputes.

### Step 3: Credible Routes the Pay-Out to the Best Local Rail

Credible connects to multiple local payout endpoints across each market, such as:

* instant bank transfer rails
* wallet networks (e.g., GCash, OPay)
* real-time payment systems (e.g., UPI-like rails)
* local banking partners and processors

Rather than relying on a single provider, Credible dynamically routes payouts based on:

* availability and uptime
* success rate performance
* cost efficiency
* corridor-specific rules and compliance needs

Your integration stays the same even as Credible adds providers or optimizes routing.

### Step 4: Instant T+0 Settlement Using Stablecoin-Backed Liquidity

Traditional payouts require prefunding local accounts or waiting for fiat settlement windows. Credible removes that constraint by using an embedded stablecoin liquidity layer.

Once the payout request is validated:

* Credible advances stablecoin-backed liquidity instantly
* payouts are executed on local rails in real time
* you receive immediate settlement confirmation (T+0)
* your users get a near-instant payout experience

This is what enables true “real-time” cross-border payouts without trapped capital.

### Step 5: Fiat Execution Completes Locally and Reconciles Automatically

While settlement to you happens instantly, Credible completes local fiat execution through domestic rails and reconciles the flow automatically.

Credible manages:

* local fiat movement and partner settlement
* FX conversion where applicable
* ledger updates and balancing
* exception handling (retries, fallbacks, reversals)

This removes operational overhead from your team and provides predictable payout performance.

### Step 6 & 7: You Get Unified Reporting, Status Webhooks, and Settlement Ledger

Credible provides full visibility and operational tooling, including:

* payout status tracking + webhooks
* unified settlement ledger across corridors
* reconciliation exports and reporting
* dispute/return handling workflows
* compliance logs and audit trails

You get a single source of truth for payouts across multiple markets—without maintaining separate PSP dashboards or country-specific ops workflows.


---

# 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/credible-overview/how-credible-works/pay-out.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.