Skip to main content
The Payment API is the part of the Quidkey API that creates payment transactions and follows them. It’s for a merchant taking payment through its own integration, and for a partner taking payment for its merchants. It holds the endpoints for:
  • creating a payment transaction, sending the customer to pay, and reading and searching payment transactions;
  • the currencies a merchant can receive and the banks its customer can pay from;
  • payment links;
  • refunds;
  • payouts, and the balances of a merchant’s bank accounts;
  • webhook endpoints, a merchant’s own and a partner’s, and the events about payment transactions they receive.

Credential

Call it with a merchant’s own credential, or with a partner’s for any of its merchants. A merchant finds its client_id and client_secret in the Quidkey Console, and a partner gets them from Quidkey. Either is exchanged for a token as Getting started shows. A merchant runs its own webhook endpoints. A partner has one endpoint, which receives the events for the payment transactions it creates.

Read First

Every endpoint follows the API’s standards: responses and links, lists, pagination and filters, errors and retries, idempotency, authentication and access and versioning. The endpoints in this tab are also in the API Reference tab, with the rest of the API.