Part 2 of 7
The Service, Payments and Integrations
6. Nature of the Service
CentPay is not a bank. Balances held in Your Wallet are not bank deposits, do not earn interest, and are not covered by any deposit protection or insurance scheme.
We do not provide investment, financial, legal or tax advice. Any information provided through the Service is for general information only, and You should obtain independent professional advice before making any financial decision.
The Service lets You accept payments in Digital Assets, hold them in Your Wallet, and send them to other CentPay merchants, to MT5 Accounts or to external wallet addresses. We are not a party to any sale or agreement between You and Your Customers.
The Company does not operate a cryptocurrency exchange and does not provide trading services. Any trading on an MT5 Account is provided by the relevant MT5 broker under its own terms.
7. Accepting Payments
You may accept payments from Your Customers in supported Digital Assets through Your integration with the Developer API, through Your deposit address, or by any other method We make available.
You are solely responsible for the goods and services You sell, including their description, price, quality, delivery and legality, and for Your relationship with Your Customers, including any refunds, returns, complaints and disputes.
You must clearly show Your Customers Your business name, the price, the Digital Asset and network they must use, and Your own terms, refund policy and privacy policy.
A payment is treated as received only when it has been confirmed on the blockchain, has passed any compliance checks and has been credited to Your Wallet. The status of a payment shown in the app, on the dashboard or in a Webhook may change while the payment is pending.
Payments sent in the wrong amount, in an unsupported Digital Asset or on the wrong network may be delayed, credited in a different amount or permanently lost. We are not responsible for such losses and may be unable to recover the assets.
Blockchain payments cannot be charged back. If You agree to give a Customer a refund, You must make it Yourself from Your own funds. We are not obliged to make refunds to Your Customers.
We may hold, delay or reject any payment that We consider suspicious or that may breach these Terms or the law.
8. Developer API and Integrations
We may issue API Keys so that You can connect Your website, app or systems to the Service. Your secret key is shown only once, when it is generated. You must store it securely on Your own servers and must never place it in public code, a web page or a mobile app.
When You generate a new secret key, Your previous secret key stops working immediately, and You are responsible for updating Your integration.
You may add an IP address so that API calls are accepted only from that address. We strongly recommend that You set one.
You are responsible for the Webhook, success and failure addresses You set, and for keeping them secure and available. Before releasing goods or services, You must check the status of the payment through the Service. A redirect to Your success page is not, on its own, proof of payment.
You must build, test and maintain Your integration in line with Our documentation, and You are responsible for any loss caused by errors in Your integration or by the unauthorised use of Your API Keys.
We may change, limit, suspend or end any part of the Developer API, and We may revoke Your API Keys if We suspect misuse or a security risk.



