PROTOCOL OF OPERATION – VIA CRYPTO HOST – API - KEY
1- Sender sends Screen or Black Screen, so the receiver checks whether the funds
are in M1 and whether the receiver server access is via Swift or Bank – FIN MT
103 Cash Transfer.
2- The Shipper must place its funds in JSON Meta file and be loaded to the
receiver's coordinates or access keys, the same ones found in the receiver's CIS.
3- The receiver has a private and automatic server working with the IPV4 and IPV6
versions, the server is also regulated by the regulatory entities of Europe, so the
company account (JP Morgan/Frankfurt-Germany) is linked to the receiver's
private server.
4- Once the sender agrees with the receiver's information and in the same way the
receiver is signed by the DOA or PGL.
5- The sender carries out the JSON files to the Crypto Host – the receiver API with
the access keys provided. This charge can last between 4 hrs. up to 24 hrs.
depending on the sender's server.
6- Once the sender has performed the load of files, you must send the load or
backup of the load that the server launches, so that the receiver can perform the
verification. These backups include: a- JSON file connected and sent files to the
receiver server, video of the initial 30 seconds and final 30 seconds of the load,
plus the black screen where the start and final load data are shown.
7- The receiver upon receiving load vouchers performs the download process, the
download time is or may exceed the time it takes the sender to load, the
download also depends on the receiver server.
8- If the sender sent the files with automatic download is not required, the sender
will be able to access the files and verify that the folders are funded or not, so
the receiver sends the SCRIP showing whether the files sent by the sender are
funded or not.
9- In the event that the sender has sent the files with final download codes, the
receiver requests the sender the final download codes so that the receiver can
send the SCRIP checking whether the files are funded or not. And in this case the
sender will be asked the black screen where the final download codes are.
10- The recipient when verifying that the files are funded, begins work on
compensation and conversion of funds to USDT ERC20. This compensation and
conversion process has a time of 6 to 7 hours after the discharge and verification
of the existence of funds.
11- The receiver when verifying that the files are funded, requested a Meet to
confirm whether the wallets in the PGL are approved and proceed to approve or
link the wallets to the receiver server to make the return to the sender and pay
fees.
12- The receiver sends the vouchers or Slach that relates payments to wallets
registered in the PGL.
KEYS ACCESS TO RECEIVER SERVER
API for this KEY
M1 format - Euro, Dollar or USDT.
the file needs to be in M1 converted to monetary I need the IP, to add ok
API name
HENRIQUES COMPANY 01
Key
668eeffdb42af00001c4a4e4
IP Access
2804:14c:128:5a49:e0ae:a8ac:bfaf:8528
Wallet Erc 20 -0xd6869f5d7407373172cbbc83ef35f673cb0861ae
Annex: If the Path does not generate or perform links to the server or demonstrates live
such information, it must send the backup documents, Checkers, Screens and Videos of
the connection and Archives to the Recipient Server for the Recipient to that
information, search for those files in the Server and download them.
