Check your CLABE usage

Each organization has a CLABE quota (1,000,000 by default). Every active CLABE — whether receiving payments or not — occupies one slot. Deleting a CLABE frees its slot immediately.

Find inactive CLABEs

Every account number tracks the timestamp of its last inbound transfer in the last_transfer_at field. Account numbers that have never received a transfer have last_transfer_at: null.

Use the no_transfers_since filter on GET /v2/account_numbers to find account numbers with no transfer activity since a given date:

curl --request GET \
     --url 'https://api.fintoc.com/v2/account_numbers?no_transfers_since=2025-12-01' \
     --header 'Authorization: sk_live_xxxxx' \
     --header 'accept: application/json'

This returns all account numbers that either never received a transfer or whose last transfer was before December 1, 2025.

Delete a CLABE

When a CLABE is no longer needed, you can permanently delete it withDELETE /v2/account_numbers/{id}. Unlike disabling, deletion cannot be undone.

curl --request DELETE \
     --url https://api.fintoc.com/v2/account_numbers/acno_Kasf91034gj1AD \
     --header 'Authorization: sk_live_xxxxx' \
     --header 'accept: application/json'

Root account numbers (is_root: true) and blocked ones cannot be deleted.

What happens after deletion

1. Inbound transfers are rejected. Any SPEI payment sent to the deleted CLABE is automatically returned to the sender.
2. Quota is freed. Your organization's account number count decreases, allowing you to create new CLABEs.
3. The CLABE is recycled. After a cooldown period (~30 days), the CLABE enters a pool and may be reassigned to any account — including accounts belonging to other organizations.
4. A webhook fires. The account_number.deleted event is sent to your configured webhook endpoints.

Disable vs Delete

If you only need to temporarily stop receiving transfers in a particular CLABE, disable the CLABE instead.