Silvatech / PaymentsDevelopers

SILVATECH PAYMENTS / BZD · BANK-HOSTED

Paid by link.
Recorded automatically.

Talk on WhatsApp
Palm Grove BakeryWhatsApp conversation
Saturday's sailboat cake.
BZD 140 deposit.View payment link

Fictional showcase · no real payment

Send the payment link.
Hosted checkout with fictional Palm Grove Bakery showcase data
Fictional showcase · no real payment
Review the BZD amount.
Card entry happens at the bank.

Silvatech never holds funds.

Card entry stays at the bank.
PL-2041 · BZD 140.00

Fictional showcase · no real payment

Post the verified result.

THE PAYMENT CHANGES. THE ROUTE DOESN'T.

Cash makes the route a target.
A link doesn't.

Illustrative route · fictional payment

recorded by itself

THE PAYMENT, TAKEN APART

One window.
Four responsibilities.

  1. 01 / THE LINK

    One link. One clear amount.

  2. 02 / THE BANK PAGE

    We never see the card.

  3. 03 / THE STATUS

    A result, not a guess.

  4. 04 / THE RECORD

    Back where the order lives.

Fictional showcase · no real payment

Hosted checkout with fictional Palm Grove Bakery showcase data
Fictional showcase · no real payment
01 / THE LINKPL-2041 · Palm Grove BakeryBZD 140.00 · cake deposit

Fictional showcase · no real payment

02 / THE BANK PAGE
Card entry happens at the bank.

Silvatech never holds funds.

Fictional showcase · no real payment

03 / THE STATUS
Payment state
Existing open payment template rendered with fictional bakery data
Ready to send; no payment recorded.

Fictional showcase · no real payment

04 / THE RECORDPL-2041 · BZD 140.00paid · posted to order #118

Fictional showcase · no real payment

LINK OUT. RECORD BACK.

A merchant's Tuesday.

Show outcomes

Illustrative day · fictional records · alternative paths for PL-2041

  1. 8AM
  2. 12PM
  3. 6PM
WhatsApp Bank-hosted Ledger

PL-2041 · paid · posted to order #118

PL-2041 · expired · resend link

PL-2041 · refunded · reversal recorded

Illustrative day complete.

PAYMENT RECORD

Palm Grove Bakery

Reference
PL-2041
Amount
BZD 140.00
Status
paid
Posted to
Order #118
Next action
posted to order #118

Fictional showcase · no real payment

Alternative states of the same fictional link, not three sales.

THE INTERFACES, AS THEY ARE

Two sides of one payment.

Two sides of one payment: step

Customer

Payment-successful receipt for ORDER-118, real 390px template with fictional bakery data

Merchant

PL-2041 BZD 140.00

Existing Django admin paid record crop: fictional PL-2041, BZD140, ORDER-118
Fictional showcase · no real payment
paid · posted to order #118
POST /api/payments/gateway-callback

{
  "orderId": "fictional-bank-reference",
  "orderNumber": "ORDER-118",
  "status": "success",
  "amount": 14000
}

Gateway notification, not a client command.
Verify server-to-server before fulfillment.

Fictional showcase · no real payment

BZD production scopeBank-hosted card entryMerchant-bank settlementDjango REST API
Developers: the exact request and callback →

THE CONNECTIONS

Start with the work.

THE USE CASES

Fit it to the day.

I'm a and I need .

Reserve a boat with a deposit link. Tours and activities →

Fictional showcase · no real payment
Restaurants

BZD 140 deposit before the kitchen commits.

Illustrative amount · fictional exampleExplore Restaurants
Hotels

BZD 140 deposit before the room is held.

Illustrative amount · fictional exampleExplore Hotels
Tours

BZD 250 deposit before the boat is held.

Illustrative amount · fictional exampleExplore Tours
Clinics

BZD 140 payment before the visit.

Illustrative amount · fictional exampleExplore Clinics
Retail

BZD 140 payment before pickup.

Illustrative amount · fictional exampleExplore Retail
Services

BZD 140 deposit before the appointment.

Illustrative amount · fictional exampleExplore Services

BUILD A LINK

Your words.
One clear request.

Illustration · nothing is created

Fictional tour operator · PL-2041

Boat reservation deposit

BZD 250.00Expires 2026-10-17

Fictional showcase · no real payment

Boat reservation deposit · BZD 250.00 · Expires 2026-10-17

Direct answer

What is Silvatech Payments?

Silvatech Payments is the BZD checkout and payment operations software used by Silvatech services. It connects an approved merchant gateway account to payment links, hosted checkout, subscriptions, callbacks, and internal operations. Silvatech does not hold transaction funds.

BEFORE YOU BUILD

Clear answers

What is Silvatech Payments?

Silvatech Payments is the BZD payment software layer used by Silvatech services. It provides payment links, hosted checkout, subscriptions, API operations, and tenant-scoped records.

Does Silvatech hold customer funds?

No. Card entry takes place on the supported bank-hosted payment page, and settlement follows the merchant's relationship with its bank. Silvatech provides the software and integration layer.

Which currency is supported?

The production payment flows are currently presented and supported in Belize dollars (BZD). Multi-currency is not currently offered.

Who can use the platform today?

The platform is built first for Silvatech services and is available for selected Belize integrations after a technical and bank-credential review.

What payment operations are implemented?

Implemented flows include payment initialization and status checks, hosted checkout, payment links, card tokenization, recurring subscriptions, pre-authorization, capture, refund, reversal, callbacks, and operational logging.

Let's add a pay link to your line.

your line · BZD ___ · paidIllustration · no real payment
Talk on WhatsApp Plan an integration
Silvatech™WOP™MarketDay™Linkyoh™Chillbout™Visit Belize™Belize Logistics™