API

Interaction between vital elements of the KoenigFinance platform is itself API-based, and we can arrange programming interfaces for payment initiation, providing access to customer accounts for third-party providers, as well as any other activities relevant for your business.

Comprehensive Payment API

Our general API set includes basic functions such as transferring funds, returning transaction history data, etc. However, depending on the nature of your business and products, you can use the KoenigFinance API for the following purposes - yours or those of your clients:

• accepting payments;
• automating payments;
• managing subscriptions;
• managing pre-approved payments;
• arranging mass payouts;
• providing white-label products (payment cards etc.);
• arranging remote verification of your clients’ customers.

Custom API functions can be added at your request to suit your specific needs.

We also provide strong detailed documentation that will make API implementation easy and smooth. It includes description of API calls, information on error handling, code samples in different languages, and other useful references.

Webhooks and Event Messaging

The KoenigFinance platform houses a messaging service that allows you to get notifications about transaction-related or other relevant events and automate your backend processing of these events. Processing API calls may take some time, but instead of keeping the system waiting idly, a message is sent to your Webhooks listener which triggers transaction status update.

To ensure Webhooks security, an authentication protocol is used to verify Webhooks messages and avoid fraud. We also provide a step-by-step guide on writing your Webhooks listener that includes code examples as well as an Webhooks Simulator test tool for making sure your listener handles messages correctly.

Security and Control

KoenigFinance employs API keys to identify who is using your API and give you control over how it is used. Individual keys can be created for each function (or group of functions) and adjusted separately for each account in the system. It is possible to allow access to API keys from a determined range of IP addresses only, or set transaction limits for payment functions.