Current scope: Silvatech Payments is not advertised as a bank, wallet, payment facilitator, merchant-account provider, or custodian of transaction funds. Integration-specific commercial and support terms are agreed separately in writing.
1. Using the service
You may use Silvatech Payments only through a Silvatech service or a selected integration that Silvatech has reviewed. You must have authority to act for the business or service connected to the account and must provide accurate integration information.
You are responsible for protecting credentials issued to you, limiting access to authorized people, and promptly reporting suspected unauthorized use through the Silvatech contact page.
2. Payment and bank boundary
The software can create BZD payment requests, hosted checkout pages, payment links, tokenized subscriptions, status checks, callbacks, refunds, reversals, pre-authorizations, and captures where the configured bank gateway supports them.
Customers enter card details on the supported bank-hosted card page. The merchant uses its own compatible, bank-approved gateway credentials, and authorization and settlement follow the merchant's agreement with its bank. Silvatech does not promise approval, settlement timing, or reversal outcomes controlled by the bank or card network.
3. Merchant responsibilities
The merchant remains responsible for the products or services it sells, accurate descriptions and BZD amounts, customer consent, fulfillment, receipts, taxes, refund and cancellation terms, dispute evidence, and compliance with laws and bank requirements that apply to its business.
You must not use the service for unlawful activity, unauthorized charges, credential sharing, deceptive transactions, attempts to bypass security controls, or payment processing on behalf of another business unless that arrangement has been approved in writing by all required parties.
4. Integration safety
You must treat callbacks as signals, verify payment status before irreversible fulfillment, use unique references and idempotent handling, validate customer-facing amounts, and keep API credentials out of browser code and public repositories.
Do not send raw card numbers, security codes, passwords, health details, or unrelated sensitive information through payment descriptions, metadata, callbacks, or support requests.
5. Fees, refunds, and disputes
No public fee schedule or payout service is offered on this site. Any Silvatech implementation or support fees must be set out in a written quote or agreement. Bank fees, settlement, chargebacks, and card disputes remain governed by the merchant's bank and applicable card-network terms.
Refund, reversal, and cancellation requests are available only where supported and authorized. A successful request to the software does not replace confirmation from the bank.
6. Availability and changes
No public uptime or response-time guarantee is offered. Maintenance, internet services, bank systems, and other dependencies can affect availability. Any service-level commitment must be stated in a separate written agreement.
Silvatech may update these public terms as the product changes. The date above will be revised when the published terms change.
7. Contact
Questions about these terms, an integration, or account access can be submitted through the Silvatech contact page. Do not include card data or secrets.