API Keys are the next major requirements for enabling seamless transactions with Blinqpay Checkout, as they are required for authenticating API calls made to our supported endpoints. Upon creating your developer account, you will have access to two separate keys: Public and Secret: which are to be used on Test and Live modes respectively.
Blinqpay authenticates your API requests using your account’s API keys. If you do not include your key when making an API request or use one that is incorrect or outdated, Blinqpay returns an error.
All API requests exist in either test or live mode, and one mode cannot be manipulated by data in the other. To get your live and test API keys sign up here
Public Keys (Publishable)
As the name suggests, public keys keys are meant solely to identify your account with Blinqpay, and do not pose any threats to your account or the apps associated with them. They can safely be published in places like your Blinqpay JavaScript code, or in an Android or iPhone app. public keys only have the power to initialize a transaction.
Secret Keys
On the other hand, secret keys are configured to retrieve all sensitive information pertaining to the holder's account ( transactions, financial data, e.t.c ). Secret keys are highly confidential and pose high risks if exposed to unauthorized personnel; hence, they should be kept secret and away from your client-side applications.
Only store on your own servers
Obtaining Your Keys
Login to your Checkout Dashboard
Navigate to Settings page, and then to API Keys and Webhooks tab
Copy-paste the keys where necessary, depending on what environment / mode you're on.