Current Pricing

Your monthly bill will be calculated as an accumulation of the following factors across all the environments in your organization:

• the platform fee you select on the pricing page 
• the number of distinct endpoints - payment gateways and receivers
• the number of API calls executed during the billing period

You can view your organization's accrued fees in the Spreedly Dashboard.

Platform Fee

All Spreedly plans include access to our custom tools, unlimited secure card storage, access to hundreds of supported gateways, and the ability to add a qualified PMD end point.

Spreedly has several pricing tiers to choose from based on your company's needs. Companies with one or two gateways might opt for the Starting plan, while companies who want to add and use myriad gateways will want to choose one of the higher plan levels. An added benefit of the plans with a higher monthly platform fee would be a lower per API call price.

Endpoints

An endpoint is a gateway (Stripe, Authorize.Net, WorldPay) or a Receiver (Clover, Mastercard, Shopify). In our most basic plan, you are allowed two endpoints, e.g. Stripe and Cybersource. Note: there are no limits on the number of merchant accounts you can have.

It is important to note that a gateway or receiver, in terms of billing, means the number of distinct types of gateways and receivers that you’ve provisioned. For instance, if you have five Authorize.net gateways retained across your organization’s environments your gateway count is one (not five).

Only retained, non-test, gateways and receivers count towards your plan’s storage limit. Gateways and receivers that are redacted cannot be used to conduct transactions and, thus, are not counted towards your plan’s limit.

To find out which gateways and receivers you have retained, you can use the Dashboard or the API. If you exceed your plan’s limit you will automatically be bumped to the next plan.

We will automatically upgrade your plan if your endpoint usage exceeds your planʼs capacity. All other upgrades and downgrade activity is done by you, manually.

API Calls

Spreedly only charges you for the API calls you make. Your choice of pricing plan will directly influence what your per-API-call fee will be. If you are a higher volume customer, it may make sense for you to pay a larger monthly platform fee to take advantage of the drastically lower per-API-call fee. 

A general rule of thumb is between 1 to 3 API calls to successfully process a credit card transaction. This will depend on whether the card is being added for the first time or is already stored, whether you’re doing an authorization too, or simply a purchase.

For example, a 3 call transaction might look like:

• Add a card
• Run an authorization retaining on success
• Run a capture

If this is a repeat/recurring transaction, it could be as simple as running a purchase, and thus be only one API call.

It's important to note that test API calls in trial accounts are free. Test API calls in production accounts, however, are metered and billed.

Legacy Pricing

Note: this next section refers to legacy pricing plans only

Your monthly bill will be calculated as an accumulation of the following factors across all the environments in your organization:

• the number of stored payment methods (cards)
• the number of distinct endpoints - payment gateways and receivers
• the number of transactions executed during the billing period on Standard Gateways and receivers

You can always view your organization’s accrued fees in the Spreedly Dashboard.

Payment methods

Only retained, non-test, payment methods count towards your plan’s storage limit. Payment methods that are redacted cannot be used to transact against a gateway and, thus, are not counted towards your plan’s limit.

Spreedly charges $100 per month for every 5,000 cards stored in your vault. To find out how many payment methods you have retained you can iterate through the payment method API or use the Dashboard. If you exceed your plan’s limit of stored payment methods you will automatically be bumped to the next plan. This will impact your monthly charge so be sure to redact unused payment methods.

Example: Your organization is on a plan which allows for 10K stored payment methods at $200 per month. You host a large event on your site which draws in 6k new customers in one day. At the end of the event, you have 16k cards in your vault. Your plan will automatically be upgraded to allow for up to 20k stored payment methods and your bill will increase by $200 per month.

Endpoints

There are two distinct endpoint types at Spreedly:

• Partner Gateways are billed at $50 per month each and incur no transaction fees. 
• Receivers and Standard Gateways are billed at $100 per month each and incur a transaction fee of $.03 per transaction.

Only retained, non-test, gateways and receivers count towards your plan’s storage limit. Gateways and receivers that are redacted cannot be used to conduct transactions and, thus, are not counted towards your plan’s limit.

It is important to note that a gateway or receiver, in terms of billing, means the number of distinct types of gateways and receivers that you’ve provisioned. For instance, if you have five Authorize.net gateways retained across your organization’s environments your gateway count is one (not five).

To find out which gateways and receivers you have retained, you can use the Dashboard. If you exceed your plan’s limit you will automatically be bumped to the next plan.

Example: Your organization is on a plan which allows for one Standard Gateway at $100 per month. You decide to add PayPal, which is a Partner Gateway. Once you authenticate the PayPal gateway in one of your Spreedly environments, your bill will increase by $50 per month.

Transactions

Although every interaction with the Spreedly API results in a transaction, billable transactions are defined only as transactions where money changes hands. The list of billable transactions includes:

• Purchases and captures against a production gateway
• Deliveries against a production receiver
• Only successful transactions (failed purchase attempts do not count.)

The billable transaction count accrues on a monthly basis and resets to zero at the beginning of every billing period.