Scribd
Upload
5 views

SWIFTNet_Server_Documentation.pdf

This document outlines the process for SWIFTNet senders to transmit signed transactions to a server for processing on the Ethereum blockchain, including optional token swaps via Uniswap. It details API endpoints, required fields for transaction submissions, and error handling procedures. Security measures such as HTTPS and Bearer token authentication are emphasized, along with the necessity of a unique SWIFT reference for each transaction.

Uploaded by

prish4life
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
5 views

SWIFTNet_Server_Documentation.pdf

This document outlines the process for SWIFTNet senders to transmit signed transactions to a server for processing on the Ethereum blockchain, including optional token swaps via Uniswap. It details API endpoints, required fields for transaction submissions, and error handling procedures. Security measures such as HTTPS and Bearer token authentication are emphasized, along with the necessity of a unique SWIFT reference for each transaction.

Uploaded by

prish4life
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/ 6

Documentation for SWIFTNet Senders: Sending Transactions to Our Serve

Overview

This document provides instructions for SWIFTNet senders to transmit transactions to our server for

processing on the Ethereum blockchain. The server will:

- Accept signed transactions sent from SWIFTNet.

- Optionally perform token swaps using Uniswap (if the token is not USDT).

- Broadcast transactions to the Ethereum blockchain.

- Monitor and track transaction status for auditing.

Our server is designed to handle secure and efficient transaction processing while ensuring that all

costs, including gas fees for Ethereum transactions, are borne by the sender.

1. Server API Details

API Base URL

The server can be accessed at the following endpoint:

http://3.66.77.192

All requests must be sent using HTTPS for security purposes if configured.

Authentication

We use a Bearer Token for authentication. You will need to include the provided token in the

Authorization header of each request.


Authorization Token: IQRdvsH1pd-PnHO_wJ3wfbqKRTfffsjc

Example Authorization Header:

Authorization: Bearer IQRdvsH1pd-PnHO_wJ3wfbqKRTfffsjc

2. API Endpoints

1. Health Check Endpoint

This is a simple endpoint to check if the server is running.

Endpoint: /health

Method: GET

Description: Verifies the server is operational.

Example Request:

curl -H "Authorization: Bearer IQRdvsH1pd-PnHO_wJ3wfbqKRTfffsjc" http://3.66.77.192/health

Response:

"Server is running"

2. Transaction Processing Endpoint

This is the main endpoint for sending signed transactions from SWIFTNet for processing on the

Ethereum blockchain.

Endpoint: /receive-swift
Method: POST

Description: Sends a signed transaction from SWIFTNet for processing. If the token is not USDT,

the server will use Uniswap to convert it to USDT before broadcasting the transaction on the

Ethereum network.

Required Fields:

- swiftReference (string): A unique reference to the SWIFT transaction.

- signedTransaction (string): The signed Ethereum transaction in hex format.

- tokenAddress (string): The Ethereum contract address of the token being sent.

- amount (numeric): The amount of tokens being transferred.

Example Request:

curl -X POST -H "Authorization: Bearer IQRdvsH1pd-PnHO_wJ3wfbqKRTfffsjc" -H "Content-Type:

application/json" -d '{

"swiftReference": "SWIFT12345",

"signedTransaction":

"0xf86b808504a817c800825208947a250d5630b4cf539739df2c5dacb4c659f2488c89056bc75e2d63

100008025a064b7003fd7f90bf8e8ad9b86fbc5a1915c1f4ba95cf850ba33cfe25436e326a5a05fa37d1

464524bc3db5db2a70685d02429e5878499e5c4c2bff9b920836582b5",

"tokenAddress": "0xdac17f958d2ee523a2206206994597c13d831ec7",

"amount": 1000000

}' http://3.66.77.192/receive-swift

Response:

If the transaction is processed successfully, the response will contain the transaction hash on the

Ethereum blockchain.
Example Success Response:

"message": "Transaction successful",

"transactionHash": "0x123abc456def789..."

Example Error Response:

"error": "Failed to process transaction"

3. Required Information from SWIFTNet Senders

1. Signed Transaction:

You must sign the Ethereum transaction on your side before sending it to our server. Ensure the

transaction includes the necessary gas fees to cover the cost of broadcasting on the Ethereum

blockchain. The server will only broadcast signed transactions; it will not sign transactions on your

behalf.

Gas fees: Ensure you include enough gas to cover the transaction on the Ethereum network.

2. Token Address:

The token address should match the ERC-20 token being transferred. If the token is not USDT, the

server will use Uniswap to swap the token into USDT.


Supported Tokens: Any ERC-20 token that can be swapped on Uniswap. However, the final

transaction will always be converted to USDT.

3. Unique SWIFT Reference:

Every transaction must be associated with a unique swiftReference to allow traceability and auditing.

This helps in tracking transactions and resolving disputes if any.

4. Procedures for Sending Transactions

Step-by-Step Process:

1. Prepare the Signed Ethereum Transaction:

Ensure the transaction is correctly signed, including gas fees and other necessary details. The

signed transaction must be in hexadecimal format.

2. Determine the Token:

Provide the correct token address. If it is not USDT, the server will perform a swap using Uniswap.

3. Send the Transaction to Our Server:

Use the /receive-swift endpoint to send the transaction, along with the SWIFT reference, token

address, and the amount being transferred.

4. Monitor Transaction Status:

Upon successful broadcast of the transaction, you will receive a transactionHash in the response,

which you can track on the Ethereum network for confirmation.

5. Error Handling and Troubleshooting


Common Errors:

- Invalid Authorization Token: Ensure you are using the correct Bearer token in the Authorization

header.

- Insufficient Gas Fees: Ensure that your signed transaction includes sufficient gas fees to complete

the transaction on the Ethereum blockchain.

- Invalid Token Address: Make sure the token address is a valid ERC-20 contract address.

Troubleshooting:

If you encounter issues, verify that:

- The signed transaction is correct and contains enough gas fees.

- The token address and other fields are valid.

- You are sending the request with the correct Authorization token.

6. Security

We use HTTPS (if configured) and Bearer token authentication to ensure secure communication

between SWIFTNet and our server.

7. Please note master wallet:

0x626503d7E46eDcb05f4B5787b53301121563E015

This wallet is the master wallet connected to our systems.


It is required to be the receiving wallet to conclude a successful transaction.

You might also like