Yes. A credit card token is never tied to any one gateway. Once you have the token for that payment method, you can run transactions against any of the gateways you have on file.
Yes. We believe it's your data, not ours. Given this is sensitive data it will need to be transferred in a secure fashion to another fully certified PCI organization.
No. We never touch your money. Instead, money flows from your customer to your gateway/merchant account.
We support the underlying currencies that your particular payment gateway(s) supports.
You can vault the cards so that you can charge the same card again in the future. So, in that sense we support recurring charges. However, you have to create the rules and code around when you want to re-charge those cards.
You can add bank accounts as payment methods in Spreedly to be used with a gateway’s eCheck service. We currently support this feature through the gateways listed here or by reviewing individual gateway support.
No. You must have an existing merchant account to use Spreedly via one of our supported gateways.
Our PCI page can help to give you an understanding of some of the basics.
Yes we are. You can find our supporting documentation on our PCI page.
By using a transparent redirect we ensure that the sensitive data never touches your servers. You can read more about how we can help on our PCI page.
While we’re not a QSA and can’t advise on PCI issues, most customers will need to provide a copy of Spreedly’s AOC and occasionally an AOC for our most recent quarterly scan plus a self-assessment questionnaire. You can find both documents and more information on the questionnaire and the process generally on our PCI page. If you have any questions specific to your business we recommend contacting a QSA
Contact Us and we'll get your questions answered. Or, check out our docs for more info.