The integration
One link. Events in, signals out.
This page is for the engineer who has to build it. Here is the shape of the whole job.
The two directions
Everything travels one of two ways.
Player events
Your platform tells PT what a player did. Registrations, deposits, sessions and bets. Each engine reads what it needs.
Signed signals
When an engine reaches a money decision, it sends one signed call. Your platform checks the signature, then acts.
What your team builds
Four pieces, and then it is done.
| Piece | What it does | Built how many times |
|---|---|---|
| Send events | Push what a player did as it happens. | Once |
| Hold the keys | One set of credentials for the link. | Once |
| Receive a signal | One endpoint that accepts a signed call. | Once |
| Act on a signal | Move the balance the signal describes. | Once |
| Add the second engine | Switch it on. | Zero new pieces |
Trust
How your platform knows a signal is genuine.
Every outbound call carries a signature.
Your side checks it before doing anything, so a
message that fails the check gets ignored.
THE CALL
Carries a signature
Computed from the message and a secret only the two sides hold.
YOUR SIDE
Checks before acting
A failed check means the message goes nowhere.
EITHER WAY
It is written down
Accepted or ignored, the attempt stays in the record.
Your platform stays the only thing that moves a player balance.
Bring an engineer to the demo.
Thirty minutes. We walk the link, the events, the signal and the signature.
hello@pt.example