[jusben1369]

It is tricky. Maybe we have more work to do. If you sign up for a single Stripe account you get a set of credentials. You drop those in to process against us. That's one payment gateway token. Say you you Stripe but also want to offer PayPal as a payment type. That's one for Stripe and 1 for PayPal (essentially two stand alone payment gateways) Ok, that's pretty vanilla. Ok, now you want to add Dwolla. That's a 3rd.

Second example. Say you are in the US and you do all your processing via Auth.Net. That's one token. Now you open a local office in Australia and want/need to process locally (say PIn Payments) That's a second token. Now you expand to the UK and use Sage Pay there (third token)

Final example. You're building the next Shopify or Freshbooks. Each of your customers will do their own processing and need their own merchant account. Each of those customers equates to one payment gateway token.

So a stand alone commmerce site with one gateway for credit cards and support for Dwolla and PayPal as a payment type = 3 tokens. The Uber model - where in each country you set up a new processor - probably equals 4 - 10 tokens. And then next Shopify = 100's to 1000's of tokens.

[throwa]

It is good you clarified this here as it wasn't clear to me and though I had before now settled on using spreedly-core, due to my not understanding that bit, I quickly began thinking I may need to evaluate other options all again. But no need with this explanation.

Why don't you paste the exact explanation/examples that you have given here in the pop-up that comes up when we mouse over 'pay as you go' in your new pricing page.

Great job.

[mattberg]

Thanks for the explanation. Those are the use cases I was kind of thinking, it just didn't seem 100% clear in the pricing page, especially when my use case would probably just be one or two tokens.

[drewjoh]

I was confused by this initially too. I think it's just "token" that throws me off. I know what a gateway is, so maybe just saying "25 Gateways" or "$10/Gateway" instead of "gateway token" might be better? Just my initial thought.

[jusben1369]

The problem we run into there is someone supports 8 gateways (for example) but has 500 customers with 500 individual merchant accounts. They might come away with the impression they just need to pay for 8 gateways. So those folks understand this but we do end up seeming overly complicated for someone who doesn't have that complex use case.