# What is Yumi

**Yumi is Credit-as-a-Service on stablecoin rails.**

We enable fintech platforms, such as consumer or business neobanks, card programs, savings apps, and payment gateways to offer credit products - installments, BNPL, and credit, without building underwriting, capital markets, or servicing in-house.

At a high level, we offer the full credit stack:

* **Underwriting & risk engine**: Evaluates applicants using multiple data sources (onchain, offchain, and traditional).
* **Financing layer**: Provides capital to fund the loans; repayments flow back to providers per agreed terms.
* **Servicing**: Handles repayment scheduling and delinquency workflows with partners.

***

### Value proposition

* Enable unsecured **credit** (BNPL, installments, or revolving) in a matter of weeks without building underwriting, financing and risk in-house.
* Yumi handles all risk and underwriting, you just get a new feature and revenue stream
* Integration takes less than a week for most teams

***

### Who this is for

Yumi is designed for platforms that already have distribution and user relationships, but lack the infrastructure to offer credit safely and efficiently.

That includes, but is not limited to:\
– Neobanks and card programs\
– Payment and checkout platforms\
– Payroll and income-linked applications\
– Business banking and invoicing/fx products\
– Savings and money management apps

***

### Vision

The future of finance is fragmentation, not consolidation.

Thousands of specialized financial platforms will emerge - each tailored to a specific audience, geography, or use case. In this world, there will be no single dominant credit card, bank, or lender. There will be thousands.

Most of these platforms will want to offer credit to deepen user engagement and increase revenue. Yet building a full credit stack from scratch remains prohibitively complex, costly, and heavily regulated.

Yumi exists to change that.

We turn credit into a composable capability - easy to integrate, scalable, and compliant - so any platform can offer sophisticated lending without becoming a credit expert.


# Risk management

### Underwriting

We underwrite the user based on:\
\- **Onchain data**: wallet assets, transaction history, DeFi activity; \
\- **Offchain data**: bank account balance, assets & liabilities, cashflow;\
\- **Exotic data sources** like criminal history, tax reports, and employment status, that we get with **zkTLS** or **Open Banking**;\
\
Using this mix allows us to get more **accurate results** than most web2 companies, as well as **serve a global audience**. 

We design **tailored algorithms** (decision tree, weights, and thresholds) **for each underwriting case**, based on the specifics of our partner integration: location, userbase, and payment target.

### Servicing & default management

We currently allow user to **repay their debt manually** or **inside our partner app** (through API). For EVM networks, we leverage our partner's infrastructure to enable **automatic recurring payments** (see [Otim Docs](https://docs.otim.com/docs/use-cases#recurring-transfers)). We plan to use more onchain protocols to optimize repayment UX in the future. 

We employ several **offline debt collection agencies** to service our debt if needed. Special agreements with our partners allow us to **restrict app or asset access** in case of delinquency. 


# Loan financing/DeFi flow

We currently use **private LP capital** to fund the credit line. For the details of the deals, please **get in touch with us directly**. 

In the **future**, we plan to use permissionless **DeFi vaults/bonds** to finance our loans.

*Buy now, pay later flow*

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

*Credit flow*

<figure><img src="/files/9eImhEqlgIHqSOqNs2pU" alt=""><figcaption></figcaption></figure>


# Opportunities Yumi unlocks

Serving as a credit infrastructure layer, we unlock a range of possibilities:

* **B2B BNPL for Suppliers and Business Banks that serve them**\
  Enables suppliers and the platforms they use for invoicing, payments, and cash management, to offer buyers deferred or installment financing - improving buyer liquidity while ensuring suppliers get paid upfront, without the platform operating as a lender.
* **Merchant and Crypto Payment Gateway BNPL SDK** \
  Traditional, **consumer-focused BNPL** in the form of a simple **SDK** where Yumi handles everything under the hood.
* **Credit Infrastructure for crypto neobanks**\
  Allows crypto neobanks to **issue unsecured loans to their customers,** with Yumi handling underwriting, capital and risk under the hood.
* **Embedded consumer installments and credit**\
  Allows consumer-facing platforms and payment flows to offer installment payments through a simple integration, while Yumi handles underwriting, funding, and servicing behind the scenes.
* **Data layer**\
  We create a programmable, **interoperable data layer** and **standard for onchain credit profiles**.


# Overview

Yumi provides infrastructure for neobanks & fintechs, allowing them to **issue unsecured consumer credit**. Yumi handles all the risk, and the **integration is minimal** - we work alongside your current infrastructure, financing logic, and support VISA/Mastercard cards. Most teams integrate our API/SDK in under a week.

### Why have a credit offering?

* **New Feature**\
  Currently, no crypto cards offer credit or uncollateralized borrowing - your card will have a strong offering that no one else does. **Be the first!**
* **New Revenue Stream**

  Capture interest spread without building your own infrastructure - Yumi handles underwriting, loan origination and servicing under the hood. **No risk for the card provider.**
* **Fewer Declines**

  If a purchase fails, the user doesn’t have to top up again and wait for it to go through. Yumi issues a loan **at the point of sale** if the user doesn’t have enough funds.

### Core benefits

* **No Liability on the card provider's side**\
  Yumi handles everything under the hood with zero risk for the card issuer.
* **Underwriting & Limits**

  Typical \~ $250 starter line; auto-increase after each clean payoff. \
  *(Although the specific limits can be discussed and adjusted based on the type of user.)*
* **Tailored Repayment Plans**

  We offer a range of options for repayments, examples are:

  * **A revolving APR** that accrues from the moment of purchase, with a max **period of 2 months.**
  * **Advance loan** structure, when the debt is repaid on a **chosen date of the next month**, together with the **flat fee (3% of the loan amount).**
  * Repaying interest with **card cashback**. \
    *(A 2% cashback can cover the interest for a \~1-month loan)*
* **Servicing & Collections**

  Yumi **automates servicing** under the hood; the card **provider is not exposed to any risk**.\
  However, we might request the ability to freeze users' assets on a card in the event of default.
* **Hands-on Integration Support**\
  Our developers will **personally help with the integration.** We’re also happy to adjust our code for the needs of the card partner.


# User flow

*Those are just example designs; everything in the images can be customized.*

#### Step 1: Choose to Issue a Credit Card

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

#### Step 2: Get an initial limit and connect more data sources (optional)

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

#### Step 3: Ready to spend!

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


# Revenue sharing model

A revenue-sharing model is discussed with each partner based on volume and other factors.


# Technical architecture

### Connecting to Yumi Credit Line

* The underwriting process is facilitated via **dedicated API endpoints** or **SDK methods** (TBD). Your system sends us users' **banking** and **wallet** data, along with any **available data**. We use it to **analyze the user's profile** and determine a credit limit.&#x20;
* Required data includes one or more **financial sources** (bank, wallet, or card), the **user's legal name**, **nationality,** and one or more **points of contact**.
* For cards with the **Mobile app**, we also plan to build a **React Native SDK** for modular integration.

After onboarding, an initial **limit is dynamically updated** based on users' and macroeconomic data.

### Loan Authorization (Per-Transaction Decision)

The card queries the API for a decision (**loan authorization**); the API returns a response with the current credit limit, approval (or rejection), and additional loan information. The model is **just-in-time underwriting**: users' **limit is checked for each purchase**; the limit may change from transaction to transaction and after repayments.

**Funding model** at authorization: the card receives the server-side **allowance signature** to withdraw funds from the Yumi hot vault, without waiting for a transfer, thereby avoiding additional **transaction delays**.

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

### Debt Repayment

There are dedicated **API endpoints** for **constructing** and **submitting** a **repayment tx**. Also, if users want to repay debt from a 3rd-party account, they can **send an ochain transaction** directly to the **dedicated wallet** or **provide us a signature** via API endpoint. We can execute the transaction on our side.


# API

At the moment of Authorization, the issuer queries the Yumi API for a credit limit using an HTTP request:

### a. Endpoint: Send a <mark style="color:orange;">POST</mark> request to the permit endpoint.

```markup
POST https://yumi-app-prod.up.railway.app/underwriting/permit
```

### b. Request Body

<details>

<summary><mark style="color:blue;">underwriteData</mark>    <mark style="color:$info;">object</mark>  <mark style="color:red;">required</mark></summary>

&#x20;    underwriteData.<mark style="color:blue;">EVMwalletAddresses</mark>    <mark style="color:$info;">string\[]</mark>  <mark style="color:red;">required</mark> \
&#x20;           <mark style="color:$info;">EVM wallet addresses of the user</mark>\
&#x20;           <mark style="color:$warning;">Example: \[ "0x123...", "0x456..." ]</mark>

&#x20;    underwriteData.<mark style="color:blue;">SOLwalletAddresses</mark>    <mark style="color:$info;">string\[]</mark>  <mark style="color:red;">required</mark> \
&#x20;           <mark style="color:$info;">SOL wallet addresses of the user</mark>\
&#x20;           <mark style="color:$warning;">Example: \[ "abc...", "def..." ]</mark>

&#x20;    underwriteData.<mark style="color:blue;">walletBalance</mark>    <mark style="color:$info;">number</mark>  <mark style="color:red;">required</mark> \
&#x20;           <mark style="color:$info;">Bank account balance of the user</mark>\
&#x20;           <mark style="color:$warning;">Example: 1000</mark>

</details>

<details>

<summary><mark style="color:blue;">permitData</mark>    <mark style="color:$info;">object</mark>  <mark style="color:red;">required</mark></summary>

&#x20;    permitData.<mark style="color:blue;">spender</mark>    <mark style="color:$info;">string</mark>  <mark style="color:red;">required</mark> \
&#x20;           <mark style="color:$info;">Executor of the permit</mark>\
&#x20;           <mark style="color:$warning;">Example: "0x789..."</mark>

&#x20;    permitData.<mark style="color:blue;">value</mark>    <mark style="color:$info;">number</mark>  <mark style="color:red;">required</mark> \
&#x20;           <mark style="color:$info;">USDC amount the user wants to loan</mark>\
&#x20;           <mark style="color:$warning;">Example: 30</mark>

</details>

{% hint style="info" %}
If the credit is approved, the endpoint returns a permit signature for the requested USDC value, enabling the issuer to withdraw funds from the Yumi vault.
{% endhint %}

### c. Response

<details>

<summary><mark style="color:green;"><strong>Success (Credit approved)</strong></mark></summary>

```json
{
    "code": 1,
    "permit": {
        "signature": {
            "v": 1,
            "r": "0x...",
            "s": "0x..."
        },
        "owner": "0x...", // Yumi vault
        "spender": "0x456...",
        "value": "40000000", // 40 USDC in decimals
        "deadline": "1719000000"
    },
    "creditLimit": 250, // USDC
    "msg": "Credit approved",
    "timestamp": 1761166681347
}
```

</details>

<details>

<summary><mark style="color:green;"><strong>Success (Credit denied)</strong></mark></summary>

```json
{
    "code": 2,
    "permit": null,
    "creditLimit": 30, // USDC
    "msg": "Credit denied",
    "timestamp": 1761166681347
}
```

</details>

<details>

<summary><mark style="color:red;">Exception (Parameter Error)</mark></summary>

```json
{
    "code": 3,
    "permit": null,
    "msg": "parameter error: {error}",
    "timestamp": 1691732593484
}
```

</details>

<details>

<summary><mark style="color:red;">Exception (System Error)</mark></summary>

```json
{
    "code": 4,
    "permit": null,
    "msg": "system error",
    "timestamp": 1691732593484
}
```

</details>


# FAQ

<details>

<summary>TLDR;</summary>

Yumi provides infrastructure for crypto cards, allowing them to **issue unsecured consumer credit**. Yumi handles all the risk, and the i**ntegration is minimal** - we work alongside your current infrastructure, financing logic, and support VISA/Mastercard cards

</details>

<details>

<summary>TLDR: How does it work?</summary>

Our **loans are purely uncollateralized**. Because we&#x20;

* **KYC** the user – knowing their identity enables debt collection and credit reporting if they default.
* Underwrite the user - we use their wallet, bank, and other data sources to **assess the risk with AI and algorithms**.

</details>

<details>

<summary>How long does it take to integrate</summary>

Most teams integrate our SDK/APIs in a week

</details>

<details>

<summary>How do you underwrite the user?</summary>

We underwrite them based on a **mix of onchain and offchain data**. The card provider can **share the available data** with us, or we can **request it directly from the user**.\
\
We use **zkTLS** and **Open Banking** to access users' credit scores, employment status, tax reports, and other data to underwrite people around the globe better.

</details>

<details>

<summary>What is the APR? Is there a revenue share?</summary>

Yumi's **APR is 14% on average,** but depends on the credit model and consumer. As a card provider, you are free to **add any markup** you want. You can configure this in our dashboard (TBD).

</details>

<details>

<summary>Does the user have to pass KYC?</summary>

**Yes.** We don't work with non-KYC cards.

</details>

<details>

<summary>How do you handle repayments?</summary>

There are **two options**: the **automated repayment** from the card account or a **manual repayment** from any account the user prefers.

</details>

<details>

<summary>How do you handle defaults?</summary>

We work with **debt collection agencies** to service the bad debt. In some cases, we can **freeze assets** on a user's account.

</details>

<details>

<summary>Would we need to issue a credit card?</summary>

No, your entire **infrastructure can stay the same**. We work with regular **VISA/Mastercard cards**. The only difference is that instead of taking the money from the user's wallet, you take it from our pool.

</details>

<details>

<summary>Do we need to change any of our existing logic?</summary>

The **integration is minimal.**\
Backend: You must call Yumi's API only during the authorization and settlement phases. We don't introduce any delay. You can read more in[API](/credit/api).\
Frontend: We will provide a **React Native SDK** for you to integrate our KYC flow into your app.&#x20;

</details>

<details>

<summary>Do we need to deploy any new smart contracts?</summary>

No. It is **backend/frontend** integration.

</details>

<details>

<summary>Do you work with both JIT and a Pre-funded model? </summary>

Yes, we **support any card infrastructure**.

</details>

<details>

<summary>What is the credit limit?</summary>

We're planning an **initial average limit of \~$500 per user**. That is **adjustable** according to the customer profile.

</details>

<details>

<summary>Who funds the user's loan? Who's responsible for defaults?</summary>

**Yumi takes on ALL the risk**. We use **private capita**l and, later, DeFi, to fund the loans. If a user defaults, Yumi eats the loss (**defaults are fully accounted fo**r in our model, so Yumi can afford to do that and remain profitable).

</details>

<details>

<summary>When does Yumi fund the loan?</summary>

We support funding both **during the authorization phase** (the card provider can pull funds from our account) and **in batches** at the end of the day (any period).\
This depends on your compliance and risk management preferences.

</details>

<details>

<summary>Is there a demo live?</summary>

Yes. Please contact us to **schedule a live demo** or get the **Loom video**.

</details>


# Overview

Yumi provides an **SDK and API** that adds "pay-in-4" to any checkout flow.

### Why Yumi's Pay-in-4?

* **Boost Conversion & AOV**

  Offering “pay 4×” **increases average order value** by 15–25 % and r**educes cart abandonment**.
* **Cut Costs & Risk**

  **Lower fee than legacy BNPLs**, plus zero chargebacks and **instant settlement**
* **Global Crypto Shopper Reach**

  Instantly accept **stablecoin-based payments from wallets worldwide**—no new banking rails needed.

### Key features

* **Drop-in Button**

  Seamlessly sits alongside other payment options.
* **Instant Settlement**

  Merchant receives full USDC (with possible fiat conversion) on purchase.
* **Customizable UI & Integration support**

  Customizable SDK - **match your look**. Our engineers help you integrate the feature end-to-end.
* **Live Dashboard**

  Track GMV, **repayment health**, and **approval rates** in real time.
* **No risk** \
  We charge a **fee per order**, so if shoppers don’t use Yumi, you don’t owe us anything. Yumi handles everything internally - underwriting, loan origination, and servicing.


# User flow

*Those are just example designs, you can check them on* [our demo](https://demo.yumi.finance). *Everything in the images can be customized.*

#### Select Yumi as the checkout option.

![](/files/CD3pnDUpaiiiEaIv7CAJ)

#### Connect bank account (optional)

![](/files/4Xx5Mw6X3KCk0LGQ7i54)

#### Connect wallet

Using [Privy](https://docs.privy.io/wallets/connectors/).

![](/files/nOZnMfyPrHHx5euSQpgX) ![](/files/oT9yoyQloeGajIxUUNzr)

#### Identity Verification (KYC)

Powered by [zkMe](https://docs.zk.me/zkme-dochub/verify-with-zkme-protocol/zkkyc-compliance-suite/zkkyc-credentials/proof-of-citizenship-zkpoc).\
![](/files/RPKq5H1iPiypR1FWJa2j) ![](/files/dqndQzoXXiCJZP8BcDph)   ![](/files/p4z9WomccwMzV5OX69uQ)

#### Select a payment plan.

![](/files/FR440QdyL8Zag9WQTJVG)

#### Pay.

&#x20;![](/files/8ia77aPER4n6eielwLdL)


# Technical architecture

### Using Yumi as a BNPL Option (Onboarding)

* The entire flow takes place **within the merchant’s or PSP's UI**; integration is achieved via the SDK, which includes theming support.
* The user can l**ink a bank account** (optional) to receive asset statements and transaction + identity data. In the US, this is done via Plaid; in other locations, we use zkTLS.
* The user can also **connect** **EVM and/or SVM wallets**.
* If a bank is not connected, the user must **complete a zkKYC**.
* At least **one financial data source** (a wallet or a bank) is required.
* We are currently working to integrate with other data sources to improve coverage.

After onboarding, an initial **credit limit** is set based on financial data and **dynamically updated**.

### Payment

* The merchant queries Yumi for a **decision (limit/approval)**; the SDK returns a **callback** with the current **credit limit, approval (or rejection),** and additional loan information. The user's limit may change from purchase to purchase and after repayments.
* The **user sends 25%** of the purchase amount to the merchant, and **Yumi sends the other 75%**.

### Debt Repayment (Installments)

**Every 2 weeks**, Yumi automatically pulls the **scheduled installment** directly from the user’s wallet using the provided allowance (onchain or offchain), until the debt is fully repaid (**3 pulls in total**). If the user’s wallet does not have sufficient balance at the scheduled time, repayment will fail, and the user may incur penalties or risk a lowered credit score.

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


# SDK


# FAQ

<details>

<summary>TLDR;</summary>

Yumi offers an SDK that can **add a “pay-in-4 with crypto”** to any checkout flow. Yumi handles all the risk, and the integration is minimal.

</details>

<details>

<summary>How long does it take to integrate</summary>

Depending on how much you want to customize it the integration can take from a couple of minutes to a week.

</details>

<details>

<summary>How do you underwrite the user?</summary>

We underwrite them based on a **mix of onchain and offchain data**. The merchant/payment provider can **share the available data** with us, or we can **request it directly from the user**.\
\
We use **zkTLS** and **Open Banking** to access users' credit scores, employment status, tax reports, and other data to underwrite people around the globe better.

</details>

<details>

<summary>What is the fee structure?</summary>

We charge a **3% merchant fee**.

</details>

<details>

<summary>Does the user have to KYC?</summary>

**Yes.** They need to prove their identity by completing a **zkKYC** (scanning their passport/ID), connecting their **bank account**, or providing **another valid form of identification**.

</details>

<details>

<summary>How do you handle repayments?</summary>

There are two options: the user either **repays manually** or signs a permit (an EIP-712 message for EVM) for Yumi to **pull funds automatically**.

</details>

<details>

<summary>How do you handle defaults?</summary>

We work with **debt collection agencies** to service the bad debt. In some cases, we can **freeze assets** on a user's account.

</details>

<details>

<summary>Is it hard to integrate? Do we need to change our code?</summary>

The integration is done via a **React SDK** that you can install within a couple of minutes and add to your existing code. The **integration is minimal.**

</details>

<details>

<summary>What is the credit limit</summary>

We're planning an **initial average limit of \~$500 per user**. That is **adjustable** according to the customer profile.

</details>

<details>

<summary>Who funds the user's loan? Who's responsible for defaults?</summary>

**Yumi takes on ALL the risk**. We use **private capita**l and, later, DeFi, to fund the loans. If a user defaults, Yumi eats the loss (**defaults are fully accounted for** in our model, so Yumi can afford to do that and remain profitable).

</details>

<details>

<summary>Is there a demo live?</summary>

Yes. Please contact us to **schedule a live demo** or get the **Loom video**.

</details>


# Overview

Yumi provides an **SDK and API** that enables **B2B Buy Now, Pay Later via Net-30 invoice terms** directly inside checkout or invoicing flows.

Suppliers get paid **immediately**, while buyers can pay **30 days later, with an option to split the payment on day 15,** with Yumi handling credit decisions, collections, and repayment operations end-to-end.

### Why Yumi’s B2B BNPL?

#### Improve Conversion & Order Size

Offering Net-30 payment terms removes buyer cash-flow friction, helping suppliers close deals faster and increase average order values — especially with new or cross-border buyers.

#### Get Paid Instantly, Eliminate Risk

Suppliers receive full settlement upfront while Yumi assumes default risk and collections. No accounts receivables overhead, no bad debt exposure.

#### Predictable, Transparent Pricing

Yumi charges a 2-5% fee on the invoice amount, paid by the supplier only when BNPL is used.

### How It Works

* **Net-30 Terms**

  Buyers pay the invoice **30 days after purchase**.
* **Controlled Exposure**

  Yumi applies **per-buyer and per-transaction limits**, starting conservatively for new buyers and increasing limits as repayment history is established.
* **SME-Focused Transactions**

  Currently supports **SME-sized invoices**, typically ranging from **a few hundred to a few thousand USD/EUR**.
* **Collections & Reminders Included**

  If a buyer fails to pay on time, Yumi manages **reminders, follow-ups, and collections**, and may negotiate short extensions with the buyer.

### Key Features

* **Drop-in BNPL Option**

  Net-30 appears seamlessly alongside existing payment methods.
* **Minimal integration**\
  Most teams get started using our API & SDK in under a week of development work
* **Instant Settlement**

  Suppliers receive funds upfront, independent of buyer repayment timing.
* **Built-in Credit Controls**

  Dynamic limits per buyer and transaction to manage risk.
* **Live Dashboard**

  Monitor GMV, outstanding invoices, repayment status, and buyer performance in real time.
* **No Operational Burden**

  Yumi handles underwriting, credit decisions, servicing, dunning, and collections — suppliers simply sell.


# User flow

#### 1. Checkout / Invoice Selection

At checkout or invoice review, the buyer selects:

* **Pay on Invoice — Net-30**

The buyer is shown:

* Total invoice amount
* Payment due date (**30 days** from purchase or shipment)

Where enabled, the buyer is informed that the invoice may be settled using a **split payment schedule** within Net-30 (two payments).

**Note**: choosing the split payment option increases reliability and trust from Yumi towards the buyer, hence allowing potentially higher limits.

#### 2. Buyer Eligibility & Limits

Yumi evaluates eligibility in real time based on:

* Buyer business identity and verification status
* Transaction amount
* Historical repayment behavior (if applicable)

Yumi applies **per-buyer and per-transaction limits**, starting conservatively for new buyers and increasing over time based on repayment history.

#### 3. Approval & Order Completion

If approved:

* The order is completed immediately
* The buyer receives an invoice displaying:
  * Invoice amount
  * Net-30 due date
  * **Split settlement schedule (if applied):**
    * **50% of the invoice amount due on Day 15**
    * **Remaining 50% due on Day 30**
  * Payment instructions

No upfront payment is required at checkout.

#### 4. Invoice Period (Day 0–30)

During the invoice period:

* No buyer action is required unless a split payment is scheduled
* Buyers may view outstanding invoices, due dates, and scheduled payments

If the split schedule is applied:

* **50% of the invoice amount is automatically collected on Day 15**
* The remaining balance continues to be payable on Day 30

Optional extensions (e.g. +15 days) may be offered according to policy and are explicitly priced.

#### 5. Payment at Maturity

On the Net-30 due date (Day 30):

* Any remaining balance (**50%**) is settled in a **single final payment**

No additional installments or amortization apply beyond Day 30.

#### 6. Late Payment Handling

If any scheduled payment is not received on time:

* Yumi manages reminders, dunning, and collections directly with the buyer
* Short extensions or payment arrangements may be negotiated where permitted


# FAQ

<details>

<summary>TLDR;</summary>

Yumi provides an **SDK and API** that enables **B2B Buy Now, Pay Later via Net-30 invoice terms** directly inside checkout or invoicing flows.

Suppliers get paid immediately, while buyers can pay 30 days later, with an option to split the payment on day 15, with Yumi handling credit decisions, collections, and repayment operations end-to-end.

</details>

<details>

<summary>How long does it take to integrate this?</summary>

It takes less than a week for most teams to integrate our API & SDK

</details>

<details>

<summary>How do you underwrite the business?</summary>

We underwrite them based on a **mix of onchain and offchain data**. The business banking platform provider can **share the available data** with us, or we can **request it directly from the business**.

</details>

<details>

<summary>What is the fee structure?</summary>

We charge a **2-5% fee on the invoice amount.**

</details>

<details>

<summary>Does the business have to KYB?</summary>

**Yes.**\
All buyers using B2B BNPL must complete **business verification (KYB)** before accessing Net-30 terms.

Depending on the integration and jurisdiction, KYB may include:

* Business registration details (legal entity, directors, UBOs)
* Verification of authorized signatories
* Proof of business activity and operating address

Where supported, Yumi can leverage **zkKYB** to verify business credentials **without exposing underlying sensitive data on-chain**.\
Only verified businesses are eligible for BNPL approval and limit increases.

</details>

<details>

<summary>How do you handle repayments?</summary>

Repayments are due according to the invoice terms (e.g. Net-30, with an optional split).

Depending on the integration, buyers can:

* **Repay manually** using supported payment rails, or
* **Authorize automatic collection**, where permitted, via a pre-approved payment instruction (e.g. signed authorization or on-chain permission)

All repayment schedules and due dates are clearly disclosed on the invoice.

</details>

<details>

<summary>How do you handle defaults?</summary>

Yumi handles defaults end-to-end. Suppliers are not involved.

If a payment is missed:

* Yumi sends reminders and follows up with the buyer.
* If the payment remains overdue, Yumi continues collection efforts and may engage professional debt collection agencies for business receivables.
* Buyers with unpaid balances may have BNPL access suspended, credit limits reduced, or be required to pay upfront for future purchases.
* Further recovery actions may be taken where permitted by law and agreed in the BNPL terms.

Suppliers are paid upfront and are not exposed to buyer non-payment.

</details>

<details>

<summary>What is the credit limit</summary>

We're planning an **initial average limit of up to $2000 per business**. That is **adjustable** according to the business' profile.

</details>

<details>

<summary>Who funds the user's loan? Who's responsible for defaults?</summary>

**Yumi takes on ALL the risk**. We use **private capita**l and DeFi to fund the loans. If a user defaults, Yumi eats the loss (**defaults are fully accounted for** in our model, so Yumi can afford to do that and remain profitable).

</details>

<details>

<summary>Is there a demo live?</summary>

Please contact us to **schedule a live demo** or get the **Loom video**.

</details>