Card Processing (also called 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.
Debit card processing may be preferable over credit card processing for:
- Funding Deposit Accounts: Use of a credit card to fund a deposit account might be considered a cash advance by some credit card companies (leading to the credit card company charging fees for your end-user).
- Purchasing Cryptocurrencies: Some credit card companies do not allow users to purchase cryptocurrencies.
- Lower Transaction Fees: credit card pulls are more expensive than debit card pulls.
- Debit Pull: Pulling funds from a debit card
- Credit Pull: Pulling funds from a credit card
- Push to Debit: Pushing funds to a debit card
- Some smaller networks such as STAR, Pulse, Accel, and NYCE.
Transaction Node Type:
- Make sure your controls (what you are allowed to do in our system) allow for at least one of our card processing transactions.
- Have an account owned by a user with
SEND-AND-RECEIVEpermission and who is not a match in one of our sanctions lists click here for a guide on how to check for this.
- Link the target external card to our system. Please look at Linking a Card for more information.
- If all the steps above have been successfully executed, you can now create a transaction.
- For Pulls you will input the
<<account_interchangeUS>>node ID of the linked card in the
node_idpath parameter and the desired recipient account in our system in the call payload.
- For Pushes, you will input the node ID of the Synapse-hosted account you wish to push funds from in the
node_idpath parameter and the
<<account_interchangeUS>>node of the desired linked card in the call payload.
Storing or transmitting card numbers requires platforms to be PCI compliant. We recommend using our Interchange UI and making the relevant API calls inside the app or website to avoid having access to card data. Please keep in mind the following considerations when using our Interchange UI:
• OAuth the user on your server, but only with scope
• Send this
oauth_key to the user's app
full_dehydrate=yes from the app
Updated 7 months ago