When to use this
Use URL POST when your system can emit a URL but can't easily make an HTTP POST request — email merges, no-code tools, SMS gateways, or static document templates. Build the URL once, drop it into the template, and every recipient gets a personalised pay-now link.
If you're writing server code, prefer the Payment Service API. It uses form-data POST, which is easier to log, sign, and observe.
Endpoint
GET https://accounts.paytia.com/api/payment_service?X-API-KEY=…&…
The API key travels in the query string as X-API-KEY. Every other field is a standard URL parameter. Don't put live keys in URLs you can't control — use dedicated sandbox keys for templated links, or request encoded keys.
Flows
Create a payment from a single URL — no JSON, no POST body, just query parameters. Useful in CRM macros, call scripts, IVR menus, and email templates.
Same as URL POST but with parameters Base64-encoded for safer transport over channels that may strip, mangle, or log plain query-string content.