Q: Do I need to transact or vault with Spreedly tokens to use the Recommendation API?
No, customers using the Recommendation API don’t need to use Spreedly to tokenize, vault, or transact. Customers using the Recommendation API don’t need to use Spreedly for their payment orchestration.
Q: Do I need a payment gateway relationship to use the Recommendation API?
No business relationship is needed to use the Recommendation service. This allows customers to test out different gateway combinations before pursuing a business relationship. Any supported gateway type can be added as a “gateway_type” API request.
Q: Do I need to transact after I receive a gateway recommendation?
No, the service provides a recommendation-only. No transaction follow-up is required, the
recommendation can be used to inform the final routing decision as-needed.
Q: How can I control my own decision making logic?
You can build custom rules and use the Recommendation API to inform your decision making. You can leverage the success rates in the Recommendation API response to drive custom routing logic.
Q: I’m building my own Payments Orchestration Layer. Can I use the Recommendation API as a routing decision microservice?
Yes, the Recommendation API is open for partners. Please contact firstname.lastname@example.org if you would like to white label the Recommendation API as a partner.