[Feature Update] Improvements in NRE Account Identification During Bank Account Addition

We have introduced an enhancement to our bank account addition flow to improve NRE bank account identification for NRI users. This change is available via the v2 Bank Account Add/Update API, which leverages multiple redundant partners to increase identification accuracy and reliability.

What’s Changing

• Bank account addition now uses the v2 endpoint, as referenced in the updated API documentation.
• The v2 endpoint supports both add and update operations through a single API.
• For NRI-marked users, we now perform an advanced NRE identification check during bank account addition or update.

Overall Flow

1. Create User

2. Complete KYC (via any supported KYC flow)

3. Mark user as NRI

   • Applicable only if the user has non-Indian KYC
   • Indian users (with Indian KYC) cannot be marked as NRI
   • Set is_nri = true after successful KYC

4. Add or update bank account using the newer v2 bank account endpoint

5. Fetch bank details

   • If is_nre = true is present in the bank object, the account is identified as an NRE account

6. Take downstream action

   • For example, request the user to add a different bank account

Updated Bank Account Flow (v2 Endpoint)

Endpoint Behaviour

• If the bank account does not exist, the request is treated as a new addition.

• If the bank account already exists, the request is treated as an update:

  • The existing bank account is marked as deleted.
  • A new bank account record is created with the updated details.

API Path: POST https://api.saber.money/api/v1/user/client_user/bank_account

Request Body

{
  "account_number": "12345678",
  "bank_code": "123456", //IFSC Code
  "account_type": "SAVINGS", //either of SAVINGS or CURRENT
  "country": "IND",
  "routing_type": "IFSC"
}

NRE Identification Logic

• NRE identification is performed only if is_nri = true for the user

  • Users must be marked as NRI after user creation and KYC approval.
  • Indian users with Indian KYC cannot be marked as NRI.

• For NRI users:

  • An advanced check is performed to identify whether the bank account is NRE

• For non-NRI users:

  • NRE identification is not attempted
  • Even if the account is identified as an NRE account, it will be rejected

Expected Behaviour

• If the bank account is identified as NRE:

  • The account is marked approved

  • Response includes the following in bank details object:

    JSON

    "is_nre": true

• In all other cases:

  • Existing approval/rejection logic applies through penny-drop name match
  • is_nre will be false by default

Touchpoints

The is_nre flag will be available in the bank details object in the following APIs:

1. Get User
2. Get Bank Account
3. Get Bank Account Status

Additionally:

• The is_nri flag is visible in the Get User API response.

Backward Compatibility & Deprecation Note

• Existing endpoints for add / update / delete bank accounts will continue to work as expected.
• However, clients are strongly recommended to migrate to the newer endpoint, as the older endpoints are expected to be deprecated in the future.