We offer a variety of payment accounts, this allows us to provide you with the proper array of solutions unique to their respective use cases. Please refer to the pages of this section for more information on the general characteristics of our payment solutions and the specifics for each payment type. Here are all the payment accounts that we currently support:

• ​ACH​

• ​Interchange​

• ​Fedwire​

• ​SWIFT​

• ​RPPS​

• ​Checks​

• ​RDC​

• ​Crypto SRNs​

ACH (ACH-US)

ACH (Automated Clearing House) payments are an electronic form of payment between US bank accounts. It is a common and cost-effective way to transmit funds. Unlike other payment types, ACH transfers are not guaranteed funds and face the risk of returns up to 60 days after the transaction settled (although most returns occur 2-3 days after). Read more about ACH Risk under Intro to Risk.

We offer Same-Day and Standard (Next-Day) ACH transfers for both ACH pushes (credits) and ACH pulls (debits).

Cutoff Times

ACH transfers have cutoff times because transactions are batch-processed by the Federal Reserve, which requires institutions to adhere to cutoff times for the transaction batches.

We will require a short additional time to process ACH transactions on our end before transmitting the transaction data to the Federal Reserve. Our cutoff times are:

Initiating Transactions

We are assuming that:

1. ACH Transactions are enabled in your spec sheet. To learn more about that, go to Intro to Spec Sheets.

2. The user you wish to enable transfers for is already in our system and has SEND-AND-RECEIVE permissions. Go to Users API Refs to learn more.

3. There is already a Deposit or Credit account created in the system where the funds need to be sent from or to.

If that is true, then here is how you can initiate ACH:

Link Account

There are two ways to link an ACH account. Either by supplying the login credentials to the user's bank account or by supplying the account and routing numbers. Both are highlighted under Create ACH Account section.

Create Transaction

The next step is to create a transaction. Either from an ACH node or to an ACH node.

Interchange (INTERCHANGE-US)

Interchange Processing pushes/pulls funds for external debit or credit cards. Interchange Transactions are near-instant, and thus much faster than alternative transaction methods. However, they expose the platform to chargeback risk and are generally more expensive than ACH transactions, especially for larger amounts, as their cost (with the exception of Push-to-Debit) is in part based on a percentage of the transferred amount. Read more about Interchange Risk under Intro to Risk.

We currently support Pulls and Pushes for Credit, Debit and Prepaid cards issued by Visa, Mastercard and some smaller networks such as STAR, Pulse, Accel, and NYCE. Please note, that not all issuers enable push to card on their side. So pushing funds to those cards will fail.

Cutoff Times

Interchange transfers do not have cutoff times because of their instant nature.

Initiating Transactions

We are assuming that:

1. Interchange Transactions are enabled in your spec sheet. To learn more about that, go to Intro to Spec Sheets.

2. The user you wish to enable transfers for is already in our system and has SEND-AND-RECEIVE permissions. Go to Users API Refs to learn more.

3. There is already a Deposit or Credit account created in the system where the funds need to be sent from or to.

If that is true, then here is how you can initiate Interchange Transactions:

Link Account

First step is to Create an Interchange Account instance in our system. Once that is done, the node will either have DEBIT, CREDIT or CREDIT-AND-DEBIT permissions. Which would guide you in what types of transfers are enabled on this card by the issuer. Go to Possible Allowed Values to learn more.

Create Transaction

The next step is to create a transaction. Either from an Interchange node or to an Interchange node.

Fedwire (WIRE-US)

Wires offer the benefit of being guaranteed funds that settle relatively quickly. Additionally, while wires are more expensive than ACH transactions, they face no return risk, making them ideal for large sum transactions or situations where return risks need to be eliminated. Due to the non-return nature of wires, they do pose some risks for the originator. Go to Intro to Risk to learn more.

We currently use Fedwire® Funds Service to for this feature.

Cutoff Times

Wire transfers have cutoff because of bank's account reconciliation obligations with the Fed. Our cutoff times are:

Initiating Transactions

We are assuming that:

1. Fedwire Transactions are enabled in your spec sheet. To learn more about that, go to Intro to Spec Sheets.

2. The user you wish to enable transfers for is already in our system and has SEND-AND-RECEIVE permissions. Go to Users API Refs to learn more.

3. There is already a Deposit or Credit account created in the system where the funds be sent from.

If that is true, then here is how you can initiate a Fedwire:

Link Account

First step is to Create a Fedwire Account instance in our system. Once that is done, the node will either have CREDIT permissions. Go to Possible Allowed Values to learn more.

Create Transaction

The next step is to create a transaction. You will be sending funds from the deposit or credit account, to the Wire node.

SWIFT (WIRE-INT)

SWIFT offers a way to send funds to family, friends and businesses outside of the US. Additionally, while wires are more expensive than domestic transactions, they face no return risk, making them ideal for situations where return risks need to be eliminated. Due to the non-return nature of SWIFT, they do pose some risks for the originator. Go to Intro to Risk to learn more.

Cutoff Times

Wire transfers have cutoff because of bank's account reconciliation obligations with SWIFT. Our cutoff times are:

Initiating Transactions

We are assuming that:

1. SWIFT Transactions are enabled in your spec sheet. To learn more about that, go to Intro to Spec Sheets.

2. The user you wish to enable transfers for is already in our system and has SEND-AND-RECEIVE permissions. Go to Users API Refs to learn more.

3. There is already a Deposit or Credit account created in the system where the funds be sent from.

If that is true, then here is how you can initiate a SWIFT transfer:

Link Account

First step is to Create a SWIFT Account instance in our system. Once that is done, the node will either have CREDIT permissions. Go to Possible Allowed Values to learn more.

Create Transaction

The next step is to create a transaction. You will be sending funds from the deposit or credit account, to the SWIFT node.

Note on Currency Conversions

We sends and receives wires in USD. Any currency conversions will be performed either by the sending financial institution (for incoming wires) or the receiving financial institution (for outgoing wires) rather than by Synapse directly. Exchange rates can differ by the currency being converted, the entity performing the currency conversion, and even by the associated correspondent bank. Please note that the exchange rates provided to you by the entity performing the conversion will likely differ from rates you may see online (e.g. from Google search results). The entity should provide proper disclosures with both the amount in USD and the amount in the foreign currency.

RPPS

​RPPS (Remote Payment and Present Service) is an electronic payment network that enables Platforms to provide bill payment services to consumers. RPPS provides electronic routing, settlement services, billing, and online research tools to facilitate electronic bill payments (including online bill payment request processing). While financial institutions currently cannot process bill payments to foreign merchants via RPPS, it is possible that such functionality may be available at a future date. While RPPS has reduced fraud risk, RPPS transactions can still return. Go to Intro to Risk to learn more.

Cutoff Times

Wire transfers have cutoff because of bank's account reconciliation obligations with SWIFT. Our cutoff times are:

Initiating Transactions

We are assuming that:

1. RPPS Transactions are enabled in your spec sheet. To learn more about that, go to Intro to Spec Sheets.

2. The user you wish to enable transfers for is already in our system and has SEND-AND-RECEIVE permissions. Go to Users API Refs to learn more.

3. There is already a Deposit or Credit account created in the system where the funds be sent from.

If that is true, then here is how you can initiate a SWIFT transfer:

Locate Biller ID

First step is to Locate ID of the Biller that you wish to connect.

Link Account

The next step is to Create a RPPS Account instance in our system. Once that is done, the node will either have CREDIT permissions. Go to Possible Allowed Values to learn more.

Create Transaction

The next step is to create a transaction. You will be sending funds from the deposit or credit account, to the RPPS node to pay the bill.

Checks (CHECK-US)

Our check allows you to issue and mail checks on demand from any Deposit or Credit account. You may use checks for bill pay because they are accepted by all services and utility providers. While Check issuance has reduced fraud risk, transactions can still return. Go to Intro to Risk to learn more.

Cutoff Times

Check transfers have cutoff because all check payments are printed and batched together once a day. Our cutoff times are:

Initiating Transactions

We are assuming that:

1. Check Transactions are enabled in your spec sheet. To learn more about that, go to Intro to Spec Sheets.

2. The user you wish to enable transfers for is already in our system and has SEND-AND-RECEIVE permissions. Go to Users API Refs to learn more.

3. There is already a Deposit or Credit account created in the system where the funds be sent from.

If that is true, then here is how you can initiate a Check transfer:

Link Account

The next step is to Create a Check Account instance in our system. Once that is done, the node will either have CREDIT permissions. Go to Possible Allowed Values to learn more.

Create Transaction

The next step is to create a transaction. You will be sending funds from the deposit or credit account, to the Check node.

RDC

Remote Deposit Capture (RDC) is a form of payment in which users can deposit a check by taking a picture of it. RDC is more convenient than depositing a check at an ATM or at a bank branch because it allows users to make the check deposit from the comfort of their home. However, it exposes the platform to standard RDC fraud and return risks, quite similar to ACH, RDC transfers are not guaranteed funds and face the risk of returns up to 60 days after the transaction settled (although most returns occur 2-3 days after). Read more about RDC Risk under Intro to Risk.

Cutoff Times

RDC transfers have cutoff times because transactions are batch-processed by the Federal Reserve, which requires institutions to adhere to cutoff times for the transaction batches.

We will require a short additional time to process RDC transactions on our end before transmitting the transaction data to the Federal Reserve. Our cutoff times are:

Initiating Transactions

We are assuming that:

1. RDC Transactions are enabled in your spec sheet. To learn more about that, go to Intro to Spec Sheets.

2. The user you wish to enable transfers for is already in our system and has SEND-AND-RECEIVE permissions. Go to Users API Refs to learn more.

3. There is already a Deposit or Credit account created in the system where the funds be credited to.

If that is true, then here is how you can initiate a Check transfer:

Create Transaction

An RDC transfer does not require creating a node, so all you need to do is to Create an RDC Transfer.

Note on Image Quality

Checks are verified by our computer vision modules and for that reason its very important to ensure that a clean image of the check is submitted to our system. The image should have all 4 corners of the check visible, without any much additional background and everything should be well lit and clearly visible.

Crypto SRNs

SRNs allow you to transfer funds from a CRYPTO-US account to an external wallet address. Currently, Synapse only supports bitcoin, ethereum and ethereum_dai.

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.

Cutoff Times

SRN transfers do not have cutoff times because of their instant nature.

Initiating Transactions

We are assuming that:

1. Interchange Transactions are enabled in your spec sheet. To learn more about that, go to Intro to Spec Sheets.

2. The user you wish to enable transfers for is already in our system and has SEND-AND-RECEIVE permissions. Go to Users API Refs to learn more.

3. There is already a Crypto account created in the system and contains a balance.

If that is true, then here is how you can initiate SRN Transactions:

Create Transaction

The first step is to Create SRN Transaction.

View Transaction Status

The next step is to wait for the transaction to get to PROCESSING-DEBIT. When an SRN transaction is in PROCESSING-DEBIT, the associated fees for the trade are also added in the transaction. You can do this by either polling View Transaction API call or Subscribing to transaction updates.

Execute Transaction

The final step will be executing the SRN transaction. The will send the transaction to the blockchain for settlement.