SILVATECH PAYMENTS / FOR-DEVELOPERS · BZD

A request out.
A record back.

POST /api/payments/initialize
Authorization: Bearer [tenant token]
Content-Type: application/json

{
  "donationId": "PL-2041",
  "amount": 140.00,
  "orderNumber": "ORDER-118",
  "description": "Cake deposit",
  "returnUrl": "https://example.invalid/return",
  "appCallbackUrl": "https://example.invalid/callback"
}

Fictional showcase · no real payment

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.

{
  "illustrativeState": "initialized",
  "reference": "PL-2041"
}

Fictional client state · no network · not a gateway payloadinitialized → pending → paid

Fictional showcase · no real payment

For developers

A practical API for the BZD payment lifecycle.

Create a payment, redirect to bank-hosted card entry, verify status, and connect the result to your Silvatech application.

Open the API reference

Initialize a payment

The request matches the current API schema.

Currency is not selected in this request. The current public production scope is BZD.

curl -X POST https://payments.silvatech.bz/api/payments/initialize \
  -H 'Authorization: Bearer YOUR_TENANT_TOKEN' \
  -H 'Content-Type: application/json' \
  -d '{
    "donationId": "BZ-1001",
    "amount": "120.00",
    "returnUrl": "https://example.bz/orders/BZ-1001/return"
  }'

Implemented endpoints

Use the operation that matches the business event.

CheckoutInitialize, hosted checkout, payment link

VerificationStatus inquiry and gateway callback

LifecyclePre-authorize, capture, refund, reverse

Repeat paymentCard token, token payment, subscription create/pause/resume/cancel

Integration rule

Callbacks are signals, not the final authority.

Store callbacks idempotently, return a timely response, and verify payment status server-to-server before irreversible fulfillment.

Delivery scope

No public callback retry SLA.

The current platform records and forwards callback data, but public marketing does not promise guaranteed delivery retries or response-time targets.

Next step

Review the exact request and response contracts.

Open Swagger Review integration notes

Let's add a pay link to your line.

Illustration · no real payment

Talk on WhatsApp Plan an integration

A request out.A record back.