Following the implementation of localized data rules in India, client experience and technical integration may change, including the storage and provision of account information and payments data. Depending on the way in which you interact with Deutsche Bank for initiating payments and receiving account information requests, some actions may be required:

DB Direct Internet (DBDI):

In case you use DBDI we do not foresee that you will need to make any changes. The domain set-up, user entitlements, payment data, templates and beneficiaries will be ported to the new India instance by us. User profiles, user credentials, administration processes to access India account information and payment processing will remain unchanged. If you have an active user preference, alerts, schedulers etc. these will be replicated into newly created India Instance by default.

Specific action for you:

✓ if you have a global domain which contains the Indian accounts and you initiate or upload payments manually, you will need to toggle between a new India instance and your existing global domain in order to view your transactions and account reporting or initiate and authorize payments.
✓ If you use the file upload or file export functionality, the files will need to be in the “India only” and “non-India” accounts in the new set-up.

EBICS Electronic Data Transmission (EDT) Services:

In case you are enabled for EBICS channel for EDT, Request for Payment execution and Account Information services, a new India instance will be created.

Specific action for you:

✓ You are required to set up user access and corporate signatures for your India instance.
✓ You are required to send a separate payment file for Indian held accounts and another file for all your other countries
✓ We will reach out to you bilaterally to provide further details on that change

DB Application Programming Interface (API):

If you are calling any DB hosted API endpoint for initiating payments related instructions from your Indian accounts, there will be a new endpoint (a new hostname) which is hosted to segregate India flows. Old hostname: https://corporateapi.db.com, New hostname: https://api.corporatebank.db.com

Specific action for you:

✓ You will need to make the relevant changes on your side to connect to the new endpoint for all API traffic as outlined above
✓ We will reach out to you bilaterally to provide further details on that change

DB Direct Connect (host-to-host):

If you are currently sending/uploading a single payment file containing debits/credits to accounts held in different countries. Under the new regulation, we will not be able to process transaction files containing information and data pertaining to accounts both in India and overseas. Where instructions are received in such instances, they will be treated as invalid and will be cancelled.

Specific action for you:

✓ You are required to send a separate payment file for Indian held accounts and another file for all your other countries
✓ India payment files incoming to global instances will be automatically relayed to India instances and information will be retained for max. 24 hrs. before being deleted from global instances.
✓ In case you receive reports, you need to retrieve these separately for India and rest of world
✓ We will reach out to you bilaterally to provide further details on that change

SWIFT-FileAct (MaCUG/Score):

In addition to segregating local Indian and other global payment files, a new SWIFT BIC Code DEUTINBB to be used for MACUG & SCORE Services with all other parameters for payment files relating to India accounts remain as is. All responses including Payment Status Reports (PSR) and Bank Statements will be received from the new BIC code. This ensures that the payment files relating to India accounts are routed to the new SWIFT India instance and stored locally in India.

Specific action for you:

✓ You are required to update your systems & stationary accordingly
✓ We will reach out to you bilaterally to provide further details on that change

SWIFT Services/FIN:

If you or your forwarding agent are exchanging payment request information or sending Money Transfer (MX/MT) messages using the SWIFT protocol to Deutsche Bank India as executing Bank, you will need to use a separate FIN channel and the new SWIFT BIC code: DEUTINBBP9V. All responses received will also come from the new BIC code.

If you are exchanging payment request information to Deutsche Bank India to relay (MX/MT) messages using SWIFT protocol to executing Banks in India, executing banks shall receive messages from new SWIFT BIC code: DEUTINBBP9V.

Specific action for you:

✓  You are required to update your systems & stationary accordingly
✓ We will reach out to you bilaterally to provide further details on that change

Aggregated Account Information Services:

If you are enabled for aggregated Bank Account information, please be informed that Account Statements for your account(s) with Deutsche Bank, India will be segregated from this service and will be delivered account wise in the existing formats.

Relationship Management Application (RMA) Exchange:

(Only applicable in case of SWIFT Service/FIN are used)
If you or your forwarding agents / execution banks on your behalf are sending or receiving Money Transfer (MT) requests, then please be informed that the new SWIFT BIC code DEUTINBBP9V will be valid without format changes to MT101 structure.

Specific action for you:

✓ You will be required to exchange the SWIFT BIC Code DEUTINBBP9V in RMA ahead of the migration date to allow for seamless data exchanges with authentication
✓ We will reach out to you bilaterally to provide further details on that change