Secure Processing
How it fits together
You create a payment_intent saying what you are charging, then a checkout_session, which gives you a URL. Your customer enters their card on a page hosted by the bank, so card details never reach your servers or ours. When the payment lands we send you a signed webhook.
That last part matters more than it looks: the bank’s own notification is not something we rely on. We re-read every payment from the gateway and sweep for anything that has not settled, so your webhook arrives whether or not the bank told us first.
Two rules that save time
Amounts are integers in the currency’s minor unit. 6000 is $60.00. No decimals cross the boundary in either direction, so there is nothing to round and nothing to argue about.
Test keys can never move real money. A key beginning sk_test_ operates on a separate set of books. Build the whole integration before anything is at stake.
Authentication
Send your secret key as a bearer token. That is the whole of it.
curl https://api.secureprocessing.app/v1/payment_intents \
-H "Authorization: Bearer sk_test_..."Where to go next
The quickstart takes a payment in about five minutes. If you already call the Belize Bank gateway directly, read moving over from a direct integration instead — it maps every endpoint you are using to its equivalent here.