Introduction
Digital Finance is a multi-channel payment platform that connects buyers, online merchants, service providers, acquirers, banks and payment processors.
Capabilities
Digital Finance provides a wide range of methods for payments processing, payouts to customers, along with other services:
- Acceptance of payments on our payment page, for merchants that are not PCI DSS certified or simply do not want to process payment card confidential data on their side. This acquiring method allows customers to accept card payments, make payments using the card token, and use Apple Pay, Google Pay™, Masterpass as well as other payment methods
- Acceptance of payments via host-2-host protocol, for merchants that are PCI DSS certified and work with payment card data on their side. In this case, payment by card or the token of a previously saved card is available
- Card tokenization, both separate card verification with tokenization as well as receiving a card token after a successful payment are possible
- Card payouts using the full card number
- Card payouts using a card token
- Other payment types
Where to begin?
First, you would need to understand which payment gateway services you will use. You can find a description of all available service types in the Services section of this documentation. This section describes the transaction process for each type of service sequentially along with examples.
A detailed description of each API method mentioned in the service documentation can be found in the API methods section.
During the integration, you may also need the References section that contains a list of transaction statuses, API error messages, failure reason codes as well as lists of test cards.
When you are ready to start the integration, we will provide you with all the necessary credentials and instructions for working with the API in test mode. This mode doesn't perform any real financial transactions and use test cards only.
Currently, the test mode is available not for all methods. Therefore, if there is no test mode for a method, the merchant is given credentials to work in production mode
Obtaining API credentials
To work with the API, you will be provided with credentials that would allow to work in a test environment:
| Name | Description | Example |
|---|---|---|
| api_url | Base URL for API requests | https://api.digital-finance.com.ua |
| account_id | Merchant account ID in the payment gateway Digital Finance | 1234 |
| wallet_id | Merchant wallet ID in the payment gateway Digital Finance. Each wallet stores a balance in a specific currency. You may have one or more wallet_id if needed | 1234 |
| point_id | Payment acceptance point ID. In some cases, you may have multiple points. Your payment page settings, a set of available services, commissions, and fraud protection settings may vary for different point_id | 1234 |
| service_id | Payment gateway service ID. Usually, several services may be available for your point (for example, internet acquiring and card payouts are separate services with a unique service_id) | 1234 |
| api_token | Secret string used for API authorization | qwerty123456 |
Moving to production
After testing is complete, a new account will be created for you to work in production mode.
You will receive a new account_id, wallet_id, point_id, api_token, as well as different service_id for each type of service. At the same time, the test account will also remain active and you can continue to use it.
Support
During the integration, you will have online access to our technical support where you can ask all your questions related to the API, if you wouldn't be able to find an answer in this documentation, while it is regularly updated, due to on frequently asked questions by merchants.
We wish you successful integration and a rapid launch into production!