Create Transaction

post
https://api.synapsefi.com
/v3.1/users/:user_id/nodes/:node_id/trans
Transactions
Please note that RDFI ACH, Wire Transactions, Internal Transactions and Card Transactions are transactions that cannot be created by the API as by the very nature of the transaction, the user accounts receive them vs create them via the API.
Go to Transaction Object Details to see all the required and optional body parameters allowed during transaction creation. Following are a few examples of various types of transactions and how to create them:
Create Transactions between Nodes
Below is an example of how to create a transaction between two nodes that exist in Synapse. If you wish to cover transaction fees, see our transaction fee resource.
HTTP
cURL
Python
JS
PHP
GO
POST /v3.1/users/5fe50a777562960078d3a5c6/nodes/5fe50b2dab6ce7004340c43a/trans HTTP/1.1
Host: uat-api.synapsefi.com
X-SP-USER-IP: 255.127.79.76
X-SP-USER: oauth_ohpVj1iwMQgqHR0ATzbGEU4fBuXOJ0FWZk28y7cD|e83cf6ddcf778e37bfe3d48fc78a6502062fc
Content-Type: application/json
​
{
  "to": {
    "type": "DEPOSIT-US",
    "id": "5fe96562c54d7b7bcda9b9da"
  },
  "amount": {
    "amount": 100.1,
    "currency": "USD"
  },
  "extra": {
    "ip": "255.127.79.76",
    "note": "Test transaction"
  }
}
curl --location --request POST 'https://uat-api.synapsefi.com/v3.1/users/5fe50a777562960078d3a5c6/nodes/5fe50b2dab6ce7004340c43a/trans' \
--header 'X-SP-USER-IP: 255.127.79.76' \
--header 'X-SP-USER: oauth_ohpVj1iwMQgqHR0ATzbGEU4fBuXOJ0FWZk28y7cD|e83cf6ddcf778e37bfe3d48fc78a6502062fc' \
--header 'Content-Type: application/json'
--data-raw '{
  "to": {
    "type": "DEPOSIT-US",
    "id": "5fe96562c54d7b7bcda9b9da"
  },
  "amount": {
    "amount": 100.1,
    "currency": "USD"
  },
  "extra": {
    "ip": "255.127.79.76",
    "note": "Test transaction"
  }
}'
//
//
//
//
Create RDC Transactions
Unlike Transactions between Nodes, for RDC transactions, both from and to nodes are part of the payload, while from is not really a node, its the RDC data:
HTTP
cURL
Python
JS
PHP
GO
POST /v3.1/users/5fe50a777562960078d3a5c6/nodes/5fe96562c54d7b7bcda9b9da/trans HTTP/1.1
Host: uat-api.synapsefi.com
X-SP-USER-IP: 255.127.79.76
X-SP-USER: oauth_ohpVj1iwMQgqHR0ATzbGEU4fBuXOJ0FWZk28y7cD|e83cf6ddcf778e37bfe3d48fc78a6502062fc
Content-Type: application/json
​
{
  "from":{
  	"type":"RDC",
  	"meta":{
  		"check_front":"data:image/gif;base64,SUQs==",
  		"check_back":"data:image/gif;base64,SUQs=="
  	}
  },
  "to": {
    "type": "DEPOSIT-US",
    "id": "5fe96562c54d7b7bcda9b9da"
  },
  "amount": {
    "amount": 500.1,
    "currency": "USD"
  },
  "extra": {
    "ip": "255.127.79.76",
    "note": "Test transaction"
  }
}
curl --location --request POST 'https://uat-api.synapsefi.com/v3.1/users/5fe50a777562960078d3a5c6/nodes/5fe96562c54d7b7bcda9b9da/trans' \
--header 'X-SP-USER-IP: 255.127.79.76' \
--header 'X-SP-USER: oauth_ohpVj1iwMQgqHR0ATzbGEU4fBuXOJ0FWZk28y7cD|e83cf6ddcf778e37bfe3d48fc78a6502062fc' \
--header 'Content-Type: application/json' \
--data-raw '{
  "from":{
  	"type":"RDC",
  	"meta":{
  		"check_front":"data:image/gif;base64,SUQs==",
  		"check_back":"data:image/gif;base64,SUQs=="
  	}
  },
  "to": {
    "type": "DEPOSIT-US",
    "id": "5fe96562c54d7b7bcda9b9da"
  },
  "amount": {
    "amount": 500.1,
    "currency": "USD"
  },
  "extra": {
    "ip": "255.127.79.76",
    "note": "Test transaction"
  }
}'
//
//
//
//
For a submitted RDC transaction to be processed, we also look for the following:
The image is clear enough to read all of the text on the front and back of the check. (i.e no glare, shadows on the check images) and all corners of the check are visible.
The check does not have “VOID” or “VOIDED” written on it.
The check is not a traveler’s check or substitute check.
The check amount is in U.S. dollars (USD).
The two amounts written on the check are for the same amount.
The routing number in the MIRC line has 9 digits.
The handwriting on the check looks consistent in all fields.
The payee’s name is the same as the Synapse account holder’s name.
The check number in the MICR line is the same as the check number in the top right corner.
The check written date is in the past.
The payer’s bank information has a logo and name.
The check has security features: microprinting on the signature line, security screen on the back of the check, and/or the words “original document” on the back of the check.
The check signature does not have any stains or gaps around it, nor a digitized appearance (pixelated), or unnecessary up and down pen strokes.
Nothing on either the front or back of the check appears forged or altered.
The check is signed on the back in the “Endorse here” section.
The signature on the back is different from the signature on the front.
“For mobile deposit only” is written on the back of the check. 
Please Note: Attempt to deposit in person before remote submittal will cause check to be declined.

If it is a cashier’s check:
The payee’s name is printed onto the check.
The bank phone number is shown on the check.
 
If it is a Deluxe or e-check:
The check does not include any confirmation requirement prior to depositing it.
Create Buy/Sell Crypto Transactions
To buy/sell crypto, designate the type of crypto that you want to buy/sell using the asset field.

To perform a limit buy (ex. set a max USD-to-BTC threshold below which you will not buy a given amount of Bitcoin), set extra.rate_limit to that maximum buying threshold. For instance, set your desired rate (extra.rate_limit) to .0002 if you wish to use each $1 of your order to purchase at least .0002 BTC (i.e. only execute the order when BTC-to-USD price is $5000 or less). The buy order will not execute if the prevailing rate is lower than your desired extra.rate_limit. And vice versa for transactions going the other way.
HTTP Request
cURL
POST /v3.1/users/6123c2edf8db934abad02c3c/nodes/6123c320ab6ce74acc7d53ec/trans HTTP/1.1
Host: uat-api.synapsefi.com
X-SP-USER-IP: 255.127.79.76
X-SP-USER: oauth_ynb1ajm2lSPhx3uMqXwA9e8dOQcBYktRsiKGTpHg|e83cf6ddcf778e37bfe3d48fc78a6502062fc
Content-Type: application/json
​
{
    "to": {
        "type": "CRYPTO-US",
        "id": "6123c33a7e08874925b2fc6c"
    },
    "amount": {
        "amount": 100,
        "currency": "USD"
    },
    "extra": {
        "ip": "255.127.79.76",
        "note": "Test transaction",
        "asset": "BTC"
    }
}
curl --location --request POST 'https://uat-api.synapsefi.com/v3.1/users/6123c2edf8db934abad02c3c/nodes/6123c320ab6ce74acc7d53ec/trans' \
--header 'X-SP-USER-IP: 255.127.79.76' \
--header 'X-SP-USER: oauth_ynb1ajm2lSPhx3uMqXwA9e8dOQcBYktRsiKGTpHg|e83cf6ddcf778e37bfe3d48fc78a6502062fc' \
--header 'Content-Type: application/json' \
--data-raw '{
    "to": {
        "type": "CRYPTO-US",
        "id": "6123c33a7e08874925b2fc6c"
    },
    "amount": {
        "amount": 100,
        "currency": "USD"
    },
    "extra": {
        "ip": "255.127.79.76",
        "note": "Test transaction",
        "asset": "BTC"
    }
}'
Create SRN Transactions
SRNs allow you to transfer funds from a CRYPTO-US account to an external wallet address. Currently, Synapse only supports bitcoin, ethereum, ethereum_dai, usdc, avalanche,  stellar, matic and flow.
SRN stands for System Resource Name. Here it's being used to define an external payment address that is not created or managed by Synapse. Currently it stands for bitcoin and ethereum wallet addresses, but later can be used for payment gateways like PayID.
HTTP
cURL
POST /v3.1/users/5fe50a777562960078d3a5c6/nodes/5fe4267d7e08870043683e75/trans HTTP/1.1
Host: uat-api.synapsefi.com
X-SP-USER-IP: 255.127.79.76
X-SP-USER: oauth_ohpVj1iwMQgqHR0ATzbGEU4fBuXOJ0FWZk28y7cD|e83cf6ddcf778e37bfe3d48fc78a6502062fc
Content-Type: application/json
​
{
    "to": {
        "type": "SRN",
        "meta": {
            "srn_type": "bitcoin",
            "srn_address": "1BvBMSEYstWetqTFn5Au4m4GFg7xJaNVN2"
        }
    },
    "amount": {
        "amount": 100.1,
        "currency": "SATOSHI"
    },
    "extra": {
        "ip": "255.127.79.76",
        "note": "Test transaction"
    }
}
curl --location --request POST 'https://uat-api.synapsefi.com/v3.1/users/5fe50a777562960078d3a5c6/nodes/5fe4267d7e08870043683e75/trans' \
--header 'X-SP-USER-IP: 255.127.79.76' \
--header 'X-SP-USER: oauth_ohpVj1iwMQgqHR0ATzbGEU4fBuXOJ0FWZk28y7cD|e83cf6ddcf778e37bfe3d48fc78a6502062fc' \
--header 'Content-Type: application/json' \
--data-raw '{
    "to": {
        "type": "SRN",
        "meta": {
            "srn_type": "bitcoin",
            "srn_address": "1BvBMSEYstWetqTFn5Au4m4GFg7xJaNVN2"
        }
    },
    "amount": {
        "amount": 100.1,
        "currency": "SATOSHI"
    },
    "extra": {
        "ip": "255.127.79.76",
        "note": "Test transaction"
    }
}'
Executing SRN
Once created, the transaction will move to PROCESSING-DEBIT status, once that happens, you can Execute the transaction. Please note that the balance of the node wont be effected in this state, as the funds are still in the wallet and the transaction has not been booked on the public chain yet. This is an anti-pattern to how PROCESSING-DEBIT status usually works in our system.
Covering Transaction Fees
By default, fees are deducted from the fund recipient. This means if you send $1, the fund recipient will receive $1 minus the transaction fee.

If you prefer to cover your user's transaction fees, pre-fund a deposit account from which fees will be deducted. Then set fees.fee to the negative of whatever the transaction fee will be, and fees.to.id to the node ID of the pre-funded deposit account.
Note: fees.fee is expected to be a float in dollars (USD).
HTTP
cURL
POST /v3.1/users/61281d15b72f862f1a97e6e2/nodes/61281d22ab6ce721377d53ec/trans HTTP/1.1
Host: uat-api.synapsefi.com
X-SP-USER-IP: 255.127.79.76
X-SP-USER: oauth_qWTA0DPUc5lC4sxjfnd9eYQLhIG8w3motKbE6uOk|e83cf6ddcf778e37bfe3d48fc78a6502062fc
Content-Type: application/json
Content-Length: 344
​
{
  "to": {
    "type": "DEPOSIT-US",
    "id": "61281d317e08873466a0e7b1"
  },
  "amount": {
    "amount": 100.0,
    "currency": "USD"
  },
  "extra": {
    "ip": "255.127.79.76",
    "note": "Test Transaction"
  },
  "fees": [{
    "fee":-0.03,
    "note": "Facilitator Fee",
    "to": {
        "id":"60be880b7e08876cd9349cf4"
    }
​
  }]
}
curl --location --request POST 'https://uat-api.synapsefi.com/v3.1/users/61281d15b72f862f1a97e6e2/nodes/61281d22ab6ce721377d53ec/trans' \
--header 'X-SP-USER-IP: 255.127.79.76' \
--header 'X-SP-USER: oauth_qWTA0DPUc5lC4sxjfnd9eYQLhIG8w3motKbE6uOk|e83cf6ddcf778e37bfe3d48fc78a6502062fc' \
--header 'Content-Type: application/json' \
--data-raw '{
  "to": {
    "type": "DEPOSIT-US",
    "id": "61281d317e08873466a0e7b1"
  },
  "amount": {
    "amount": 100.0,
    "currency": "USD"
  },
  "extra": {
    "ip": "255.127.79.76",
    "note": "Test Transaction"
  },
  "fees": [{
    "fee":-0.03,
    "note": "Facilitator Fee",
    "to": {
        "id":"60be880b7e08876cd9349cf4"
    }
​
  }]
}'
In the response, you will see two fees: one positive & one negative (corresponding with our Synapse-owned node & your pre-funded node respectively).
Please note that this payload only applies to transactions initiated via the API. To cover incoming wire fees from an EXTERNAL-US node, update your wire fee preferences in the dashboard.
View Transaction
Create Batch Transactions
Last modified 25d ago