Start here
New to the Paytia API? Two short reads cover the ground before you touch any endpoint:
- Getting started — base URLs, request format, how sandbox differs from live.
- Authentication — how X-API-KEY works, IP whitelisting, rotating keys.
The APIs
Four APIs cover the full product surface. Most integrations only need the first one.
Our main payment API. Create payment links, take MOTO payments, capture card details over the phone, run recurring billing and more. One endpoint, many scenarios, all driven by the transaction flag.
A lightweight GET-style API where parameters travel as URL query string. Useful for quick integrations where your system can't easily POST JSON — mail merges, low-code tools, SMS templating.
Push a click-to-dial number into a phone system so an agent can launch an outbound call in one click. Pairs with the Paytia ACA for outbound payment collection flows.
Verify whether an agent is currently on an active call before initiating a payment session. Stops payment flows starting mid-transfer, mid-IVR, or against the wrong agent.
Reference
The shared bits that apply across every endpoint:
- Webhooks — what we send you when payments complete, fail, or move state.
- Error codes — every HTTP code you can get back and what each one means.
- Exception handling — what to do when things go sideways.
- Field reference — searchable dictionary of every field we accept.
Getting API keys
Keys are gated. We issue sandbox credentials to anyone who asks — so you can read these docs, build against the try-it explorer, and evaluate the API without talking to sales. Live credentials are issued once you're onboarding as a customer.