Technical architecture

Using Yumi as a BNPL Option (Onboarding)

• The entire flow takes place within the merchant’s UI; integration is achieved via the SDK, which includes theming support.

• The user (optionally) links a bank account to provide statements and account data; in the US, this is done via Plaid.

• User can also connect their EVM and SVM wallets.

• If a bank is not connected user needs to do a zkKYC.

• At least one financial data source (wallet or bank) is required.

• We are currently working on integration with other sources of data.

After onboarding, an initial credit limit is set based on bank data; this limit is then dynamically updated.

Payment

• The issuer queries the Yumi SDK for a decision (limit/approval); the SDK returns a callback with the current loan limit/decision. The user's limit may change from transaction to transaction and after repayments.

• User sends 25% purchase amount to the "Payment Gateway", the other 75% is sent by Yumi.

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.