Skip to main content
Every Buckspay payment - regardless of account model, gas mode, or network - follows the same three-phase flow. Understanding this model makes the rest of the API predictable.

​
The pay shortcut

client.pay(calls) chains all three phases in a single call. It is equivalent to:
Use the three-step form when you need to insert backend validation between sign and send - for example, to check that the intent has not expired or that the amount is within a pre-approved tolerance.

​
Where the BFF fits

The SignedIntent that comes out of sign() is safe to POST to your backend: it carries no private key material. Your server validates business rules, then calls server.send(signed) - using a server-side createBuckspayClient configured with the buckspayFacilitator API key. The API key never leaves the server. See Facilitator and BFF for the full pattern.

​
Next

Facilitator and BFF

How the relayer works and why the API key must stay server-side.

Account models

Which account type to use and how they affect the sign step.