Supported Gateways

Use this page to find a supported gateway and choose the right resource for evaluation or implementation.

Gateway resources

Spreedly provides a unified API across many gateways, but each gateway has its own supported features, regional constraints, and required fields. Use Gateway Fact Sheets and Gateway Guides together when you evaluate and implement a gateway.

Gateway Fact Sheets

Use the Fact Sheet during discovery and architecture. It gives you a high-level technical summary of what a gateway can and cannot do in Spreedly.

Use the Fact Sheet to answer:

  • Does the gateway support transaction types such as authorize, capture, void, and credit?
  • Does it support features such as 3DS or Apple Pay?
  • Which countries does it support?
  • Which credentials do you need to add it to your Spreedly environment, such as api_key, merchant_id, or password?

Gateway Guides

Use the Guide during implementation and testing. It explains how to structure requests correctly for that specific gateway.

Use the Guide to understand:

  • Gateway-specific fields you must or may include in requests, such as gateway_specific_fields: { "stripe": { "statement_descriptor": "..." } }
  • Gateway-specific behaviors, such as verify-before-purchase flows or Level 2/3 data requirements
  • Setup steps such as webhook configuration or IP allowlisting, when required

Recommended workflow

  1. Review the Fact Sheet to confirm feature support and collect the required credentials.
  2. Add the gateway in Spreedly using the API or dashboard.
  3. Review the Guide for required fields and gateway-specific fields, then update your request payloads.
  4. Run sandbox tests and confirm your success and error handling work as expected.

Direct gateways

Offsite gateways