Skip to main content

Authentication

There are two credentials that show up in Echezona's dashboard and docs. Most integrations only need one of them.

API key — always required​

Every API request must carry your API key as a Bearer token:

Authorization: Bearer <your-api-key>

Get it from Settings > API Keys in your dashboard. See Auth for the full reference, including the pre-generated token flow used by a few dedicated endpoints.

Public Key / RSA encryption — usually not required​

Your dashboard also exposes a Public Key, and there's a Data Encryption guide describing how to RSA-encrypt sensitive fields with it. This only applies to specific client-side flows where sensitive data (like raw card details) is handled directly in your frontend.

If you're using any of the following, you can ignore the Public Key entirely and skip the Data Encryption guide:

The one exception is Core API Integration, where you build your own checkout UI and do need the Public Key to encrypt sensitive data before calling MakePayment. That integration method also requires relevant licenses and compliance certifications — see its page for details.