Add logic to CLABEs

Reject all transfers directed to any specific CLABE.

There are different ways to use your Fintoc CLABE. You can assign a CLABE to a specific user's payments or create a single-use CLABE for specific payment orders. This guide shows how to update your CLABE to make payin handling easier.

Disable a CLABE

If you disable a CLABE, all payins directed to it will be automatically rejected and returned to the sender. This way, if a CLABE is no longer intended to receive payments, by disabling it you no longer need to worry about handling stray inbound payments.

If you disable a CLABE, all payins directed to it will be automatically rejected and returned to the sender. If a CLABE is no longer intended to receive payments, disabling it prevents you from handling stray inbound payments.

Example use cases

  • Your company assigns one CLABE per user and Jared has completed offboarding from your app. Disable Jared's CLABE so payments made for Jared's user are automatically returned and don't waste your operational resources.
  • Your company assigns one CLABE per order and Richard bought a computer at your store. Disable Richard's computer order CLABE once he has paid to avoid receiving a double payment. If Richard misses the payment confirmation notice and pays twice, the money will be returned automatically and won't waste your operational resources.

Disabling a CLABE with our API

account_number = client.v2.account_verifications.update(
  "acno_Kasf91034gj1AD",
  status="disabled"
)
const accountNumber = await fintoc.v2.accountNumbers.update(
	"acno_Kasf91034gj1AD",
  status: 'disabled'
);
curl --request PATCH \
     --url https://api.fintoc.com/v2/account_numbers/acno_jKaHD105H \
     --header 'Authorization: sk_test_jKaHdEa3mfmP0D105H' \
     --header 'accept: application/json' \
     --header 'content-type: application/json' \
     --data '
{
  "status": "disabled"
}
'