Authentication
Use a secret application key as a bearer token on server-to-server requests.
Developer docs
Use application credentials from your Developer Dashboard. Keep secret keys server-side and use a unique idempotency key for supported POST requests that move money.
/api/v1/checkout/sessionsCreate a hosted checkout session.
/api/v1/paymentsInitiate a supported merchant payment.
/api/v1/transfersInitiate an account transfer.
/api/v1/transactionsRead transaction history available to the application.
/api/v1/wallets/me/balancesRead supported wallet balances for the linked account.
/api/v1/exchange-ratesRead currently active exchange-rate records.
/api/v1/withdrawalsInitiate a supported withdrawal request.
/api/v1/refundsCreate an eligible business refund.
Use a secret application key as a bearer token on server-to-server requests.
Reuse the same idempotency key only when retrying the same logical request.
Verify the SawaPay signature before trusting an incoming event.