api-doc.wecrosso.com Open in urlscan Pro
47.113.53.12  Public Scan

Form analysis
0 forms found in the DOM

Text Content

Sorry, we need js to run correctly!
OpenApi

CONTENTS
Get started
01.Authentication
POST
new token
02.Webhook
POST
register a new webhook
DEL
delete webhook by id
GET
query webhook by id
GET
query registered webhook
GET
get example of callback event
03.Wallet
POST
create a wallet
POST
modify wallet info
POST
upload KYC file
POST
submit for KYC
GET
query a wallet
04.BankAccount
GET
query wallet accounts
POST
create account
GET
query details of the specified account
GET
query funding accounts of the specified account
GET
query account balance
GET
query the account entry
05.FundsIn
GET
query funds in order
GET
page query FundsInOrder
POST
refund Funds In order
06.SecureTransfer
07.TransferRecipient
08.Transfer
09.DocumentFile
10.OperationTicket


Powered by Apifox




GET STARTED


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.


2. OVERVIEW OF PLATFORM CAPABILITIES#

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:

 1. EasyEuro merchants;
 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 and needs to be re-acquired after more than
30 minutes ( 1800s) .
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 error

When 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"
}



4. SERVICE DESCRIPTION#


5.1 CREATE WALLET FOR CUSTOMER#

 1. Get access token
 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
 5. Submit request for KYC
 6. Wait for the kyc review. After KYC approval, the system processes the result
    through webhook callback registered in step 2.


5.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

1. Introduction
2. Overview of platform capabilities
3. Interface description
3.1 Interface instructions
3.2 Interface rules
3.2.1 Authentication
3.2.2 Special Note
3.2.3 Error codes
HttpStatusCode:
4. Service Description
5.1 create wallet for customer
5.2 funding to wallet account
ApifoxBuilt by Apifox

Report