Use Case

Multiple CLABEs linked to your account enable you to implement seamless, tailor-made payment flows.

Pay-Ins

Figure 1 depicts a pay-in scheme in which each user can have a single deposit-only CLABE. This CLABE serves as both an identification tag for their pay-ins and the sole channel through which they can complete deposits. Users cannot make withdrawals through this CLABE.

The flow is as follows:

1️⃣ The Juno account holder creates the users' CLABEs with the help of the Mass Payments API.
2️⃣ The account holder shares the created CLABEs with their users; this assignment is not part of the API's
      functionality.
3️⃣ End users deposit MXN funds into the Juno account via the SPEI® network using their assigned CLABE.
4️⃣ Deposits automatically initiate the issuance of an equivalent 1:1 amount of the MXNB stablecoin.
5️⃣ The service credits the issued amount of MXNB tokens to the Juno account balance. The CLABE used to
      make the pay-in remains as the identifier of the funds.

Payouts

Figure 2 illustrates how a Juno account holder can process payouts on behalf of users using funds previously deposited and held in the MXNB account balance.

The flow is the following:

1️⃣ End users hold an MXNB balance and request an MXN payout.
2️⃣ The Juno account holder consolidates these requests and redeems the equivalent amount of
      MXNB tokens via an API call.
3️⃣ In response to the API request, Juno converts the MXNB tokens to fiat MXN.
4️⃣ The service deposits the converted funds into the previously configured external bank accounts.
5️⃣ Third parties receive payments in MXN in their bank accounts.