PHP SDK

composer require beexar/sdk

Zero runtime dependencies — no bcmath, no gmp, no HTTP client. PHP 8.1+.

Source: github.com/beexar-games/beexar-php · Reference: README

---

What it gives you

Two halves, and the second one is the work.

• Client — launch a real-money or demo session, read the catalogue. Signs every request over the exact bytes it sends.
• WalletServer — the four callbacks. You implement four methods against your own ledger; the SDK does signature verification over the raw body, parsing, validation, decimal money and the Twirp error envelope.

It also ships a complete reference wallet (~250 lines) with correct idempotency and tombstones, and the conformance fixtures every Beexar SDK is tested against.

The three things that decide whether it works

1. The raw body. The signature is an HMAC over the exact bytes received. Any middleware that parses the JSON and serialises it again destroys them. The SDK’s framework bindings exist to prevent that, and when a signature fails for that reason the SDK says so in plain words instead of leaving you with a 400.
2. Idempotency. id_provider is the platform’s idempotency key. A repeat must return the transaction id and balance you stored the first time. That check has to be in the same database transaction as the balance update — so the SDK deliberately does not do it for you.
3. Money. Decimal strings in the currency’s main unit. The SDK’s money type cannot be built from a float.

Caution

Your handler has 15 seconds. The platform retries 5xx and timeouts for up to 30 seconds with the same id_provider; it does not retry insufficient funds, bet limits, bad requests or signature failures.

Next

• The full README on GitHub has the complete API and worked examples.
• Reference wallet — what a correct implementation looks like.
• Integration Test Game — 29 scenarios against your live callbacks. This is the proof.