Terms and Conditions

B. USAGE OF RAYA API - PRODUCTION

These Terms and Conditions for the usage of Raya API Services shall be legally binding on PT Bank Raya Indonesia, Tbk, hereinafter referred to as Bank, as the first party; and users of Raya API Services, either for individual use or as a representative of a non-individual institution (e.g., legal entity, business enterprise, et cetera) that, in accordance with a Letter of Proxy or any other valid legal document, has been assigned as representation, hereinafter referred to as Partners, as the second party; in accordance with the terms and conditions stated herein. Partners agree to be subjected to the terms and conditions of Raya API Services.

1. Definitions

  1. Bank shall mean PT Bank Raya Indonesia, Tbk, including its Head Office, Branches, Sub-Branches and other offices which constitute inseparable parts of PT Bank Raya Indonesia, Tbk.
  2. Raya API (Bank Raya Application Programming Interface) shall mean a type of service which connects banking Services/services owned by Bank Raya with Services/services owned by customers, both individual and non-individual customers, to the effect that the customers are able to create their own application-based Service/service that is directly integrated with Services/services owned by Bank Raya.
  3. Partners shall mean customers that have been registered as users of Raya API Services.
  4. Customers shall mean individuals, legal entities and/or other institutions having a fund deposit account in the Bank.
  5. Consumers shall mean users of Partners’ products who are facilitated to access Bank Raya Banking Services through API.
  6. Corporate ID shall mean a code in Raya API granted to Partners for the purpose of identifying their enterprise/institution that must be inputted when accessing Raya API.
  7. Raya API Support shall mean informational/assistance services related to Raya API Services and can be contacted via email rayaapi@bankraya.co.id.
  8. Password shall mean a combination of letters (uppercase and lowercase) and numbers which constitute a confidential code that must be inputted when accessing Raya API Services.
  9. User ID Holder shall mean an individual who is granted authority by Partners to access Raya API Services.
  10. User ID shall mean an account granted to Partners for the purpose of identifying an individual that has been granted the rights to access Raya API that must be inputted when accessing Raya API Services.
  11. User Checker shall mean an account granted by Bank Raya to its employees who have the authority and responsibility to check and verify application settings in Services and submissions of productions created by Partner Users.
  12. User Approver shall mean an account granted by Bank Raya to its employees who have the authority and responsibility to grant approval for submissions of productions created by Partner Users.

2. Consumer Data Protection

  1. Partners shall ensure the existence of a written (via electronic or non-electronic media) and/or verbal (recorded) approval or consent from Consumers to the processing of data.
  2. Partners shall use Consumer data only for one or several specific purposes that have been communicated to and approved by Consumers.
  3. Partners shall be responsible for, without limitation, accuracy, completion, and consistency of data submitted through Raya API services.
  4. Partners shall maintain confidentiality of data to ensure that data usage can only be accessed by concerned parties and is not abused by unauthorized parties. 
  5. In the event of any data leakage, Partners shall independently take full responsibility to administer and handle the data leakage, which include without limitation:
  • Identification and investigation to determine the severity of the data leakage.
  • Submission of report on the data leakage to the Bank.
  • Handling of loss occurred due to data leakage.

3. Administration of Registration, Modification and Deletion of Data

  1. For any event of registration, modification, or deletion of data and/or status from the identity of Partners, User Checker or Approver, and features, Partners must complete Raya API Form or other letters and documents as determined by the Bank.
  2. The Bank shall check and verify the completeness and accuracy of data in the Raya API Form and supporting documents.
  3. The Bank may reject and return the form to be completed by customers if any inaccuracies or incompleteness of supporting documents is found.
  4. The Bank shall perform the registration, modification, or deletion into the system after checking and verification of forms and supporting documents have been conducted. Approval of registration, modification, or deletion shall be the authority of the Bank in accordance with results of checking and verification and compliance to internal Bank regulations.

4. Login/Access to Raya API Production

  1. Raya API Services may only be accessed through the website address https://developers.bankraya.co.id
  2. To access Raya API Services, the following steps must be taken:

 

  • Inputting User ID
  • Inputting Password
  • Completing captcha

5. Facilities/Services of Raya API

  1. Types of the provided Raya API Services and facilities shall match the services selected/registered as stated in the Raya API Registration Form.
  2. The Bank provides Raya API support facility to address complaints and reports via email rayaapi@bankraya.co.id.

6. Account

  1. Account used for Inquiry or Transactional facilities must first be registered in the Raya API Services.
  2. Types of accounts eligible to be registered shall be account opened in the Bank, which include current account (giro) or account in the name of the Partner.

7. Submission of Raya API Production

To access Raya API production data, Partner applicant must:

  1. Be a customer of Bank Raya and has opened a Current Account in the name of the Partner
  2. Select the desired price package
  3. Complete the Application Letter for Service Usage by stating the Persons in Charge of the API, as follows:
  • Project Manager
  • Person in charge of the API key
  • Person in charge of the API secret key
  • Person in charge of the API password key and the API secret key
  • Person in charge of API transactions or data exchange
  • Person in charge of API integration
  • Person in charge of document administration and confidentiality
  • Person in charge of fraud indications
  1. Agree to the terms and conditions of Raya API
  2. Complete the Proxy Letter for Account Debiting
  3. Attach the UAT results document
  4. Attach administrative documents, which include:
  • Name of enterprise
  • Trade name/brands (if any)
  • MCC (Merchant Category Code)
  • Address of enterprise
  • Correspondence address, including email
  • National Merchant ID
  • Account information (Bank Raya Account Name and Number) 
  1. Attach legality documents, which include:
  • Copy of documents used as basis of establishment of the institution, including amendments (Articles of Association, Deed of Establishment)
  • Copy of legalization and permit documents that are still in effect and issued by relevant institutions
  • Original letter of assignment by Service User issued by the enterprise
  • Copy of Tax ID Number (NPWP)/tax withholding slip
  • Copy of Business License (SIUP)
  • Copy of Business ID Number (NIB)
  • Copy of certificate of domicile
  • Copy of Certificate of Company Registration (TDP)
  • Copy of letter of stipulation as Taxable Entrepreneur
  • Copy of cover and current account of deposit in Bank Raya
  • Original proxy letter for account debiting
  • Name of enterprise owner (copy of the latest ID card)
  • Name of person in charge and management of the enterprise (copy of the latest ID card)
  1. Send the complete documents by uploading them via the Partnership page.
  2. Pay the production submission fee in accordance with the selected price package and attaching the proof of transfer via the Partnership page.
  3. Agree to the draft agreement of collaboration.
  4. Every assigned or authorized User ID Holder must have an active email address that has been registered to the Bank.

8. Usage of User ID and Password

  1. User ID Holder must maintain the security of User ID and Password using, without limitation, the following:
    • ​​Maintaining the confidentiality of User ID and Password
    • Not writing nor storing User ID and Password in a written format or in a computer application which may enable detection by unauthorized partie

  2. Any consequences, risks, and liabilities caused by the abuse of User ID and Password shall be the full responsibility of Partners and the Bank is indemnified against all charges.

  3. Partners shall be fully responsible for all transaction instructions that occur based on the usage of User ID and Password.

  4. Partners must immediately notify the Bank in the event that User ID and Password are detected by unauthorized parties. Any transaction instruction that occurs based on the usage of User ID and Password prior to the receipt of said written notification by the Bank shall be the full responsibility of Partners.​​​​​​​​​​​​​​

9. Blocking of User ID

  1. User ID shall be blocked if incorrect User ID and/or Password were inputted three times consecutively.
  2. Partners may apply for unblocking of User ID via the contact page in the Raya API developer portal.
  3. Unblocking of User ID shall be performed by User Checker.

10. General Terms on Transactions

  1. Partners must fill in all data necessary for each transaction in a truthful, complete, and accurate manner. Partners shall be responsibility for the truthfulness, completeness, and accuracy of the instruction and shall indemnify the Bank against all outcomes arising from the incompleteness of transaction instruction/data from Partners.
  2. Partners must ensure that User ID and Password used for Raya API application are not duplicated and abused in any form whatsoever.
  3. The Bank shall receive and conduct every instruction from Partners as a valid proof of instruction based on usage of User ID and Password. To that effect, the Bank shall not be obligated to examine or investigate the authenticity or validity or authority of the User ID and Password, or to review or prove the accuracy and completeness of the instruction, therefore the instruction shall be deemed as valid and binding on the Partners along with all outcomes that arise.
  4. Partners may only conduct transaction prior to the cut-off time that has been determined by the Bank.
  5. Regarding transactions involving Bank Indonesia or any other third party, the transactions shall comply with business days of Bank Indonesia or any other third party.
  6. The Bank reserves the right to not conduct any instruction from Partners in the event of the following:
  • Insufficient balance in the registered account.
  • The Bank knows or has enough reason and evidence to suspect that there has been or will be a fraud or crime.
  • The Bank receives orders from authorized parties.
  1. Partners shall indemnify the Bank against any responsibility on any loss occurring from usage of Raya API and Raya API tools that deviates from the instructions contained in the Raya API manual/documentations.
  2. Partners shall acknowledge ownership by the Bank of copyrights and any other intellectual property rights contained within Raya API.
  3. Partners are prohibited from duplicating or forwarding any or all rights, benefits, or obligations related to the facilities to any other party without a prior written approval from the Bank.
  4. Partners shall not disrupt, modify, alter, or abuse the entirety of the Raya API applications in any way whatsoever.
  5. Partners shall be subjected to terms related to charging of Raya API transaction and administration fees and/or hit/call fees that have been determined by the Bank.
  6. Partners fully agree and indemnify the Bank against any and all fees, damages, losses, liabilities, and/or expenses both directly and indirectly caused by violation by Partners of their obligations related to these facilities, or by any outcome that arises from and/or relates to the usage of Raya API applications.

 

11. Fees and Payments

  1. Partners hereby authorize the Bank to debit Partners’ Bank account to conduct the transaction instructed by Partners through Raya API facilities and for payment of fees arising from Raya API applications as determined by the Bank. 
  2. The Bank reserves the right to debit administration/subscription fees and/or certain transaction fees and/or any other fees arising from Raya API applications which will be determined and notified by Bank Raya.
  3. In the event of processing failure on the effective date of transaction not caused by any failure by the Bank, applicable fees shall continue to be charged to Partners.
  4. The Bank reserves the right to modify the amount of fees at any time by issuing notifications through commonly accepted means. Any modification on fees is binding on the Partners.
  5. All debiting of fees shall be conducted automatically by the system by debiting the Partners’ accounts, unless stated as manually recorded. In the event that, in an automatic recording system, the balance in the Partners’ accounts is not sufficient, the fees shall remain the obligation of the Partners until such obligations are met.
  6. Said authority of the Bank shall remain in effect insofar as the Partners still receive Raya API Services or Partners still have obligations to the Bank despite no longer receiving Raya API Services.

12. Force Majeure

  1. Partners shall indemnify the Bank against any claims or charges in the event that the Bank is unable to conduct, partially or entirely, Partners’ instructions due to events or causes beyond the control or power of the Bank, including without limitation, natural disasters, wars, riots, malfunctions of tools, system, or transmission, power disruptions, telecommunication disruptions, government policies, and any other events or causes beyond the control or power of the Bank.
  2. The Bank shall not be held responsible in the event of damages to the Raya API applications and/or tools caused by Partners’ failures or other causes including without limitation, component failure and the like, broken cables/wires, damages to computer hardware, et cetera.

13. Termination of Services

Raya API Services shall be terminated by the Bank in the event of:

  1. Partners terminate the usage of Raya API Services by submitting a Raya API facilities closure request letter and attaching necessary documents as determined by the Bank.
  2. The Bank suspects abuse of Raya API Services by Partners in connection with a violation of the law.
  3. The Bank executes a requirement or order from an authorized official or in compliance with the prevailing laws and regulations.
  4. The Bank on its sole discretion and interest decides to terminate the provision of Raya API Services to Partners by notifying the Partners through commonly accepted means. 

To reactivate the Raya API Services terminated by the Bank as in point 1 above, the procedure for new Partner registration must be followed.

14. Miscellaneous

  1. Partners shall be subjected to the terms and conditions applicable to the Bank and to the terms and conditions governing all services and transactions covered by Raya API, including any amendments, which shall be notified by the Bank through commonly accepted means.
  2. The Bank at any time at its discretion may modify the Raya API operating manual and shall notify the Partners on modifications through commonly accepted means.
  3. The Bank reserves the right to suspend Raya API Services in a temporary manner or for a certain time as determined by the Bank when the Bank is experiencing disruptions or for the purpose of update, maintenance, or any other purposes deemed good by the Bank, and the Bank shall not be held liable for the aforementioned to any party whatsoever. The Bank shall notify the Partners on the temporary suspension through commonly accepted means.

15. Modifications to the Raya API Terms and Conditions

Bank Raya at any time at its sole discretion has the rights to modify, complete, or replace the terms and conditions herein without any prior approval from the Partners. Any modifications to the terms and conditions shall be notified subsequently to the Partners through commonly accepted formats and means. Any modification to the terms and conditions herein shall be binding on the Partners.