May and June were productive months for us at Synapse. We added quite a few new features. Here is the list:
Here are some of the new features we launched in May and June:
? Instant Auth now available for ACH
We now support Instant Auth for ACH debit transactions as well. This will enable developers to launch zero balance accounts on top of Synapse with ease.
To learn more, go to Transaction Decisioning.
? UAT Testing for Direct Debit and Credit Transactions
Developers can now test ACH, Wires, and Internal Transfers more comprehensively on UAT. The new API supports lots of customizations like changing posting_label, addenda, company_id, etc.
To learn more, go to Dummy Transactions.
? Delivery Carrier now available on Shipments
Now you can view the delivery carrier for the cards that are being shipped using our APIs. Currently, we are supporting USPS, FedEx, and UPS.
To learn more, go to Shipment Object Details.
? Email support for Wallet Activations
Now end-users will get an option to pick between their phone number or email to activate the linked card with their Apple/Google/Samsung Wallets.
To learn more about our mobile wallets feature, please go to Mobile Wallets.
? Dynamic Wallet Art Selection Enabled
Now you can dynamically choose which wallet art to load into an end user’s Apple/Google/Samsung Wallet. Just like card art for physical cards, we need to pre-approve all wallet arts and assign ids to all. Approved wallet style ids will be available in your Spec Sheet just like your card style ids.
To learn more, go to Subnet Object Details.
? (UAT Only) Monthly Transaction Limits on Cards
Now developers can program dynamic monthly transaction limits on cards as well. Just like daily_cash_limit and daily_transaction_limit, now monthly_cash_limit and monthly_transaction_limit will enable you to set up dynamic monthly limits on cards.
To learn more, go to Subnet Object Details.
? Disabling Dynamic Card Limits
Now you can also set daily_cash_limit, daily_transaction_limit, monthly_cash_limit and monthly_transaction_limit to null. When null, the card limits will default to your program limits.
To learn more, go to Subnet Object Details.
? Interchange Reversals
Now we support interchange reversals for interchange pull transactions. This will enable developers to not have to create an interchange push if they wish to process a return.
To learn more, go to Cancel Transaction.
? Multiple MCC Support
For acquiring (INTERCHANGE-US) we are now able to support multiple merchant category codes. So if you are providing cash advances and also account loads in the same application, we will now be able to support different MCCs for both use cases, helping to increase approval rates on card acquiring.
Please note, we need to pre-approve both MCCs before they can be utilized. Approved MCCs will be available in your Spec Sheet for use and will be programmed by us behind the scenes for appropriate CIP tags.
