1. Introduction#
This document describes EasyEuro's API capabilities, which facilitates EasyEuro's merchants and partners to quickly and easily access European financial services.
The main readers of the document are the merchants and partners' business experts and technicians who cooperate with EasyEuro and third-party technical service providers.EasyEuro financial cloud service platform (SaaS) is based on distributed technology, mainly provides customers and partners with the following capabilities:
A. Multi-currency accounts and sub-accounts in European mainstream countries;
B. European local collection and China-Europe cross-border dispatch capabilities;
C. European local channels to pay;
D. Currency exchange ability
Please contact it_support@easyeuro.eu if you have any question of the API documents.3. Interface description#
3.1 Interface instructions#
There are three types of users who use EasyEuro’s open interface:2.
Institutional partners (PSP, Payment Service Provider) holding payment licenses;
3.
EASYEURO's channel agent;
After the user passes the compliance review of EASYEURO, EASYEURO will assign API access parameters to the user.3.2 Interface rules#
3.2.1 Authentication#
A. Message interface
Our message interface use Restful webservice, based on HTTPS protocol transmission. The interface authentication obtains the accessToken through AppKey and AppSecret. All interfaces except the authentication interface need to have the access token obtained by the authentication interface in the HttpHeader, with a field in the http common header: Authorization: Bearer ,The access token is valid for 30 minutes.
B. File interface
The file interface uses csv format file interaction, which is transmitted based on the SFTP protocol. EasyEuro opens an SFTP account for the organization. The organization uses the SFTP account to pull statements and settlement reports. EasyEuro whitelists the server IP addresses called by the organization.3.2.2 Special Note#
The new version of the interface requires that the Request-Id be added to the header of each request to ensure the uniqueness of the request, which can be generated using UUID and other methods. It is currently not required, and may be changed to required in subsequent iterations. In order not to affect the interface call, please update it in time.3.2.3 Error codes#
When the HttpStatusCode is 200, the request is successful, and the response body is the request resource object in JSON format.HttpStatusCode:#
400 Bad request - example: request parameters error
401 Unauthorized
404 Not found - endpoint or resource not exist
500 Server errorWhen HttpStatusCode is not 200, ErrorInfo in JSON format is returned:
Example:
HttpStatusCode: 400{
"code":"InvalidArgument"
"message":"name can not be empty"
"reason":"NotEmpty"
"source":"name"
}
ResponseErrorCode:#
InvalidArgument: argument is invalid, please check the request argument
IllegalState: request is not supported at current state
RepeatedRequest: request is repeated
NotAllowPartnerId: request is not allowed, please contact Customer-Support
ResourceNotFound: the requested resource is not found
IncorrectCredential: the credential is incorrect
SignKeyException: the sign key is incorrect
SystemError: EasyEuro system error, please contact Customer-Support
4. Service Description#
4.1 create wallet for customer#
2.
Register webhook to receive the callback notification:Wallet、Account、TransferOrder、FundsInOrder
3.
Create a wallet with customer basic information
4.
Upload related customer document files
6.
Wait for the kyc review. After KYC approval, the system processes the result through webhook callback registered in step 2.
4.2 funding to wallet account#
1.
Create accounts according to the currency for wallet, Result will be notified through the registered webhook
2.
Get accountName, rountingCode(SWIFTCode/BIC/SortCode) and accountNumber(iban/accountNumber) of the account
3.
Customer transfer money to the account created in the wallet from their other bank account
4.
If the wallet receive the money, FundsIn information will be notified through the registered webhook
5. Main Activity Flow#
5.1 deposit activity flow#
5.2 withdraw activity flow#
Modified at 2023-12-21 02:47:04