> 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-in.md).

# Pay-in

Credible enables global fintechs, neobanks, and internet businesses to collect payments across emerging markets using native local payment methods, while delivering instant T+0 settlement through stablecoin-backed liquidity.

Instead of building separate integrations, prefunding local accounts, and waiting days for settlement, businesses can plug into Credible’s orchestration layer and move money across borders in real time.

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

### **Step 1: Customers Pay Using Local Methods**

Credible supports the most widely used payment rails in emerging economies, including:

* **UPI** (India)
* **Pix** (Brazil)
* **GCash** (Philippines)
* **OPay** (Nigeria)
* Local bank transfers and wallet networks

This allows merchants to accept payments in local currencies through the methods consumers already use every day.

### **Step 2: Credible Orchestrates Collection Across Multiple Providers**

Behind the scenes, Credible connects to a network of:

* local payment processors
* banking partners
* wallet aggregators
* on/off-ramp providers

Rather than depending on a single PSP, Credible dynamically routes each transaction across the best available rail based on:

* success rates
* uptime
* cost and FX efficiency
* compliance requirements

Merchants integrate once through a single API, while Credible manages all local complexity underneath.

### **Step 3: Payment Confirmation Happens Locally**

Once the customer completes the payment via UPI, Pix, or a wallet rail, Credible receives a real-time confirmation event.

At this point, the payment is verified locally — even though fiat settlement through the banking system may still take additional time.

This is the key architectural shift:

**Credible separates payment confirmation from settlement delays.**

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

As soon as the pay-in is confirmed, Credible advances stablecoin-backed liquidity to the merchant instantly.

Merchants receive settlement in:

* USD
* EUR
* Stablecoins

This happens in real time (T+0), without waiting for traditional bank settlement cycles.

Credible effectively provides short-term settlement financing, bridging the gap between:

* instant local payment execution
* delayed fiat settlement finality

### **Step 5: Fiat Funds Settle Asynchronously and Reconcile Automatically**

While the merchant has already received funds instantly, Credible completes the fiat collection flow through local rails in the background.

Once the fiat funds are fully received:

* the credit exposure is closed
* balances are reconciled
* treasury and ledger records are updated

This removes the need for merchants to manage prefunding, working capital buffers, or fragmented settlement operations.

### **Step 6: Unified Reporting, Compliance, and Treasury Abstraction**

Credible provides a full-stack pay-in infrastructure layer including:

* unified settlement ledger
* transaction monitoring and fraud controls
* KYB/KYC enforcement
* compliance-aware routing
* consolidated reporting across markets

Merchants get a predictable and scalable collection system across emerging economies, without building country-specific payment operations.
