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_numbers.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"
}
'

Set inbound transfer amount limits

You can set boundaries to restrict which inbound transfers your CLABE accepts. If a transfer does not meet these criteria, Fintoc rejects it. Rejected transfers do not appear on your account statements and do not incur fees.

Feature	Description
Minimum amount	Set `min_amount` to reject any transfer with an amount lower than this value.
Maximum amount	Set `max_amount` to reject any transfer with an amount higher than this value.
Exact amount	Set both `min_amount` and `max_amount` to the same value to reject any transfer that does not match that specific amount.

Setting limits via API

account_number = client.v2.account_numbers.create(
  options={
    min_amount=300,
    max_amount=400
  }
)

const accountNumber = await fintoc.v2.accountNumbers.create(
  options: {
  	max_amount: 300,
  	min_amount: 400
  }
);

curl --request POST \
     --url https://api.fintoc.com/v2/account_numbers \
     --header 'Authorization: sk_test_jKaHdEa3mfmP0D105H' \
     --header 'accept: application/json' \
     --header 'content-type: application/json' \
     --data '
     {
     "options": {
     	max_amount: 400,
     	min_amount: 300
     }
   }
'

Home

Resources

Payments

Transfers

Direct debit

Movements

Add logic to CLABEs

Disable a CLABE

Example use cases

Disabling a CLABE with our API

Set inbound transfer amount limits

Setting limits via API

​Disable a CLABE

​Example use cases

​Disabling a CLABE with our API

​Set inbound transfer amount limits

​Setting limits via API

Disable a CLABE

Example use cases

Disabling a CLABE with our API

Set inbound transfer amount limits

Setting limits via API