Scribd
Upload
1K views2 pages

Process S2S

The document outlines a detailed process for transferring funds using different methods (S2S, SSH, Global Server) involving multiple steps such as sending API details, confirming operations, exchanging CIS, preparing and signing PGLs, and making payouts in USDT ERC20 or FIAT. Each method has specific requirements and steps, including video confirmations and scheduled operations. The processes emphasize the importance of security and verification at each stage to ensure successful fund transfers.

Uploaded by

Bernard TATTEGRAIN
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
1K views2 pages

Process S2S

The document outlines a detailed process for transferring funds using different methods (S2S, SSH, Global Server) involving multiple steps such as sending API details, confirming operations, exchanging CIS, preparing and signing PGLs, and making payouts in USDT ERC20 or FIAT. Each method has specific requirements and steps, including video confirmations and scheduled operations. The processes emphasize the importance of security and verification at each stage to ensure successful fund transfers.

Uploaded by

Bernard TATTEGRAIN
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

Process S2S

API Address
The funds are download and converted in M1 funds (originally M0 funds)

The funds are located on private server or Global server

1- Receiver sends his API details to the Sender,


2- Sender sends the black screen and the video of the “Download and conversion”,
3- Receiver confirms he can do the operation and give the ratio (usually 30+5),
4- Receiver and sender exchange the CIS,
5- Sender prepares the PGL and signs it, with 3 or 4 wallets (1 or 2 for the sender depending of the amount and
1 for each consultants side),
6- Receiver completes the PGL with his wallet and signs it,
7- Receiver sends the video of the Master wallet where all the wallets are registered,
8- Sender and Receiver schedule a Windows time for the operation to give the codes (Final and release code),
9- Receiver makes the payout in USDT ERC20 (max 8 hours after windows time).

SSH (Non converted funds)


The funds are in M0 funds non converted

The funds are located on private server

1- Receiver sends the SSH details to the sender,


2- Sender sends the black screen of the funds,
3- Receiver confirms he can do the operation and give the ratio (usually 30+5)
4- Receiver and sender exchange the CIS
5- Sender prepares the PGL and signs it, with 3 or 4 wallets (1 or 2 for the sender depending of the amount and
1 for each consultants side),
6- Receiver completes the PGL with his wallet and signs it,
7- Sender uploads the files (CEF, DLL, FIN) on private server on the receiver (SSH port 22), video of the
complete upload provided to Receiver,
8- Receiver confirms the upload on his server by video,
9- Receiver downloads and converts the funds from M0 to M1, video or screen shot of the “Download and
converted” send to the sender,
10- Receiver uploads the funds on his crypto host,
11- Receiver sends the video of the Master wallet with all the wallets are registered,
12- Sender and receiver schedule a Windows time for the operation to give the codes (Final and release code),
13- Receiver makes the payout in USDT ERC20 (max 8 hours after windows time).

This process could be done without crypto host and pay out in FIAT (EUR or USD) by bank wire transfer if both
parties agreed. (Point 10, 11 and 13 modify by bank wire transfer specify in the PGL)

SSH (Converted funds)


The funds are in M0 funds and converted

The funds are located on private server

1- Receiver sends the SSH details to the sender,


2- Sender sends the black screen and video of Download and converted funds,
3- Receiver confirms he can do the operation and give the ratio (usually 30+5)
4- Receiver and sender exchange the CIS
5- Sender prepares the PGL and signs it, with 3 or 4 wallets (1 or 2 for the sender depending of the amount and
1 for each consultants side),
6- Receiver completes the PGL with his wallet and signs it,
7- Sender uploads the files (CEF, DLL, FIN) on private server on the receiver (SSH port 22), video of the
complete upload provided to Receiver,
8- Receiver confirms the upload on his server by video,
9- Receiver uploads the funds on his crypto host,
10- Receiver sends the video of the Master wallet with all the wallets are registered,
11- Sender and receiver schedule a Windows time for the operation to give the codes (Final and release code),
12- Receiver makes the payout in USDT ERC20 (max 8 hours after windows time).

This process could be done without crypto host and pay out in FIAT (EUR or USD) by bank wire transfer if both
parties agreed. (Point 10, 11 and 13 modify by bank wire transfer specify in the PGL)
Global Server
The funds are download and converted in M1 funds (originally M0 funds)

They are located on Swift.net

1- Receiver has to prove he has access to Swift.net by sending a video showing it (TRN provide by the sender),
2- Sender sends the updated black screen and the screenshot of the “Download and conversion”,
3- Receiver confirms he can do the operation and give the ratio (usually 30+5),
4- Receiver send the CIS with crypto host Informations,
5- Sender send CIS,
6- Sender prepares the PGL and signs it, with 3 or 4 wallets (1 or 2 for the sender depending of the amount and
1 for each consultants side),
7- Receiver completes the PGL with his wallet and signs it,
8- Receiver sends a video of his crypto host where all the wallets are registered,
9- Sender and Receiver schedule a Windows time for the operation to give the codes (Final and release code)
10- Receiver makes the payout in USDT ERC20 (max 8 hours after windows time).

No TNT message allowed

You might also like