SILVATECH PAYMENTS / DOCS · BZD

A payment path,
documented.

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

Developer docs

Exact API contracts and the operating notes around them.

Use the generated API reference for request and response schemas. Use these integration pages for the BZD, bank-hosted card entry, callback, and settlement boundaries.

Open Swagger docs Open ReDoc

Customer payment