Payment Accounts
Last updated
Was this helpful?
Last updated
Was this helpful?
To provide the right solution for your use case, we offer a variety of payment accounts. Please refer to this section for more information on our payment solutions and specifics for each payment type. These are the payment accounts we currently support:
ACH (Automated Clearing House) payments are an electronic form of payment between US bank accounts. They are 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 is settled (although most returns occur within 2-3 days). Read more about ACH Risk under .
We offer Same-Day and Standard (Next-Day) ACH transfers for both ACH pushes (credits) and ACH pulls (debits).
ACH transfers 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:
ACH Type
Cutoff Time
Settlement Time
Same Day
11:00 AM PT
Same Business Day Transactions sent after the cutoff time will be included in the Next Day ACH batch at 3:00 PM PT. Same-Day pricing will still apply.
Next Day
3:00 PM PT
Next Business Day Transactions sent after the 3:00 PM PT cutoff time will be included in the following business day's ACH batch.
We are assuming that:
If that is true, then here is how you can initiate ACH:
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.
Interchange transfers do not have cutoff times because they are processed near real-time and can sometimes take up to 30 minutes to settle.
We are assuming that:
If that is true, then here is how you can initiate Interchange Transactions:
Wire transfers have cutoff times because the bank's have account reconciliation obligations with the Fed. Our cutoff times are:
Cutoff Time
Settlement Time
12:00 PM PT
Same Business Day Domestic Wire transactions sent after the cutoff time will be processed the following business day.
We are assuming that:
If that is true, then here is how you can initiate a Fedwire:
Wire transfers have cutoff times because the bank's have account reconciliation obligations with SWIFT. Our cutoff times are:
Cutoff Time
Settlement Time
9:00 AM PT
Same Business Day International Wire transactions sent after the cutoff time will be processed the following business day.
We are assuming that:
If that is true, then here is how you can initiate a SWIFT transfer:
We send and receive 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.
Wire transfers have cutoff times because the bank's have account reconciliation obligations with RPPS. Our cutoff times are:
Cutoff Time
Settlement Time
1:00 PM PT
Same Business Day Transactions sent after the cutoff time will be included in the following business day's RPPS batch.
We are assuming that:
If that is true, then here is how you can initiate a RPPS transfer:
Check transfers have cutoff times because all check payments are printed and batched together once a day. Our cutoff times are:
Cutoff Time
Settlement Time
3:00 PM PT
Will vary by the external bank the check is being deposited to. Once the check has been deposited, the bank will hold the funds for a period of time before clearing the check.
We are assuming that:
If that is true, then here is how you can initiate a Check transfer:
RDC transfers 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:
Cutoff Time
Settlement Time
3:00 PM PT
Credits for RDC transactions are issued and settled in 6 business days by default. This timeline can be slightly reduced, but doing so will significantly increase your exposure to NSF returns which occur within the first 3 business days following deposits.
We are assuming that:
If that is true, then here is how you can initiate a RDC transfer:
Checks are verified by our computer vision modules and for that reason it's 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 additional background and everything should be well lit and clearly visible.
The RDC image processing system does use advanced processing techniques such as image orientation, cropping and noise reduction to help eliminate manual reviews of check images and allow faster processing overall.
Internal transfers do not have cutoff times because they are near real-time and can sometimes take up to 30 minutes to settle.
We are assuming that:
They are trying to move money between two Synapse managed nodes.
If that is true, then here is how you can initiate Internal Transactions:
ACH Transactions are enabled in your Spec Sheet. To learn more, go to .
The user you wish to enable transfers for is already in our system and has SEND-AND-RECEIVE permissions. Go to API Refs to learn more.
There is already a or account created in the system where the funds need to be sent from or to.
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 section.
The next step is to . Either from an ACH node or to an ACH node.
Storing or transmitting card numbers requires platforms to be . So please do not store card numbers in your system unless you are PCI compliant.
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 .
Interchange Transactions are enabled in your Spec Sheet. To learn more, go to .
The user you wish to enable transfers for is already in our system and has SEND-AND-RECEIVE permissions. Go to API Refs to learn more.
There is already a or account created in the system where the funds need to be sent from or to.
The first step is to 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 to learn more.
The next step is to . Either from an Interchange node or to an Interchange node.
Wires offer the benefit of being guaranteed funds that settle relatively quickly. 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. Because they can't be returned, wires do pose some risks for the originator. Go to to learn more.
We currently use for this feature.
Fedwire Transactions are enabled in your Spec Sheet. To learn more about that, go to .
The user you wish to enable transfers for is already in our system and has SEND-AND-RECEIVE permissions. Go to API Refs to learn more.
There is already a or account created in the system where the funds need to be sent from.
The first step is to instance in our system. Once that is done, the node will have CREDIT permissions. Go to to learn more.
The next step is to . You will be sending funds from the deposit or credit account, to the Wire node.
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 to learn more.
SWIFT Transactions are enabled in your Spec Sheet. To learn more, go to .
The user you wish to enable transfers for is already in our system and has SEND-AND-RECEIVE permissions. Go to API Refs to learn more.
There is already a or account created in the system where the funds need to be sent from.
The first step is to instance in our system. Once that is done, the node will have CREDIT permissions. Go to to learn more.
The next step is to . You will be sending funds from the deposit or credit account, to the SWIFT node.
(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 to learn more.
RPPS Transactions are enabled in your Spec Sheet. To learn more, go to .
The user you wish to enable transfers for is already in our system and has SEND-AND-RECEIVE permissions. Go to API Refs to learn more.
There is already a or account created in the system where the funds need to be sent from.
The first step is to that you wish to connect.
The next step is to instance in our system. Once that is done, the node will have CREDIT permissions. Go to to learn more.
The next step is to . You will be sending funds from the deposit or credit account, to the RPPS node to pay the bill.
Our checks allows you to issue and mail checks on demand from any or 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 to learn more.
Check Transactions are enabled in your Spec Sheet. To learn more, go to .
The user you wish to enable transfers for is already in our system and has SEND-AND-RECEIVE permissions. Go to API Refs to learn more.
There is already a or account created in the system where the funds need to be sent from.
The next step is to instance in our system. Once that is done, the node will have CREDIT permissions. Go to to learn more.
The next step is to . You will be sending funds from the deposit or credit account, to the Check node.
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. Similar to ACH, RDC transfers are not guaranteed funds and face the risk of returns up to 60 days after the transaction is settled (although most returns occur within 2-3 days). Read more about RDC Risk under .
RDC Transactions are enabled in your Spec Sheet. To learn more, go to .
The user you wish to enable transfers for is already in our system and has SEND-AND-RECEIVE permissions. Go to API Refs to learn more.
There is already a or account created in the system where the funds need to be credited to.
An RDC transfer does not require creating a node, so all you need to do is to .
With Internal Transactions you can transfer funds between Synapse managed nodes (eg. , , etc.) in near real-time.
Internal Transactions are enabled in your Spec Sheet. To learn more, go to .
The user you wish to enable transfers for is already in our system and has SEND-AND-RECEIVE permissions. Go to API Refs to learn more.
The first step is to , and there are no second steps 🙂.