All eight clients create sales and payouts, look up and list payments, manage payment links, request and track refunds, and verify webhook signatures. Store the order reference and a stable idempotency key before sending a write. A successful HTTP response can still describe a pending or declined payment. First payment · Payment states
For operations outside your SDK’s method list, including usage billing, use the HTTP reference. For a browser checkout, use the checkout widget or cashier. Keep the merchant key on the server.
Server SDKs
Server SDKs
Integrate merchant payments, payouts, refunds, payment links and signed webhooks in your backend language.
Choose the client for your server. Each SDK uses the HTTPS API origin assigned to your merchant, your merchant ID, and a test or live API key. Obtain the package or source distribution from your OrsunPay integration contact.