Use Cases

Multiple CLABEs linked to your account enable you to implement flexible payment flows.

Use Case 1

Figure 1 depicts the scheme where the account holder (Bitso partner) assigns a different CLABE to each end user. The relationship between CLABEs and users is one-to-one, which means the partner can give only one CLABE to each user.

The flow is as follows:

1️⃣ The partner creates the user CLABE.
2️⃣ The partner shares the created CLABE with the user.
3️⃣ The end user deposits MXN funds through their CLABE into the partner's account, which the service credits to the account balance. Using the CLABE, the partner can identify the deposits made by each user.
4️⃣ The partner can send payments to vendors or other users when the funds are available. They can use one of two options to make these payments:

• Transfer the received MXN funds.
• Convert the received MXN funds into a digital asset and transfer the crypto funds obtained from this conversion.

It is not compulsory to transfer a received deposit. The funds can remain in the partner's account to serve other purposes.

Use Case 2

Figure 2 illustrates a second possible scheme. The partner assigns a CLABE to a vendor and shares it among users.

The flow is very similar to the former one:

1️⃣ The partner creates the vendor's CLABE.
2️⃣ The partner shares the created CLABE with their users.
3️⃣ End users deposit MXN funds through this CLABE into the partner's account, which the service credits to the account balance. Using the CLABE, the partner can identify and group all the deposits made for this vendor.
4️⃣ The partner can send payments to the vendor when the funds are ready. They can use one of two options to make these payments:

• Transfer the received MXN funds.
• Convert the received MXN funds into a digital asset and transfer the crypto funds obtained from this conversion.

More schemes are possible, for example, having a hybrid of the two explained: some CLABES assigned per user and others per vendor.