Advanced Vaulting is here, read more →

Articles in this section

Need to make a request to Spreedly?

  1. Request a new gateway integration
  2. Request 3DS on an existing gateway integration
  3. Request a gateway-specific field
  4. Request a new payment method receiver endpoint

Request a new gateway integration

While we are always open to adding support for new gateways on Spreedly, we are currently integrated to 100+ gateways that span the globe and offer a variety of existing options for customers to choose from.
 
For Spreedly to consider new gateway additions, the existing customer would need to contact our Customer Success team to provide the following:
  • What are your blockers to using existing Spreedly gateways?
  • Is the gateway a requirement of your transaction flow or a preference?
  • Do you agree to pay the one-time up front cost of a new gateway implementation?
  • What is the requested timeline for the gateway? Please note: the timeline for implementation can vary greatly depending on the responsiveness of the gateway's technical team, the current size of our development queue, and the complexity of the integration. 
  • A contact name and email address at the gateway.
  • Any API/technical documentation for for the gateway.
 
It's important to note that, if Spreedly decides to add your requested gateway, an integration can several months and this integration period should be accounted for in any go-live plans you may have.
 

Request 3DS on an existing gateway integration

While we are happy to consider adding a new 3DS integration for you, there are costs and considerations before moving forward. New integration requests are reviewed on a case by case basis for technical compatibility and business fit, and the integration fee (explained below) must be collected in full if the integration is approved.

1. If you have a relationship with a 3rd party 3DS provider (like Cardinal Commerce), we can add them via Flex. With this method, you can start transacting much quicker than adding a new Spreedly integration from scratch.

2. The one-time cost of a new 3DS implementation to be paid up front by you, the customer.

3. The timeline for implementation can vary greatly depending on the responsiveness of the gateway's technical team, the current size of our development queue and complexity of the integration.

If you have fully considered the above and wish to move forward, please reach out to us with the following information:

  • Is 3DS a requirement of your gateway/transaction flow or is it a preference?
  • What are your blockers to using existing Spreedly 3DS integrations?
  • Please provide us with an e-mail address for your contact at the gateway as well as their 3DS technical documentation.

Request a gateway-specific field

Spreedly is happy to consider the addition of gateway-specific-fields for current Spreedly customers. 
 
We require the following for all requests:
  • The gateway name
  • The use case for adding the new field
  • The gateway documentation for integrating the field(s) of interest

To submit your request, please contact the Support team.

 

Request a new payment method receiver endpoint

 
If you’d like to work with a non-gateway endpoint that we don’t currently support, we will need some information about your receiver:
  • the receiver name and/or company name
  • a link to their public site
  • the production URL you will be invoking with Spreedly payment data
  • optional - the sandbox/test URL
After receiving this information, it usually only takes about two weeks to begin transacting against your receiver’s API with real cardholder data.
 
Contact Support to make a request.

 

Was this article helpful?
Have more questions? Submit a request
Return to top

Related articles