This is worrying. We are planning to move to stripe hence I have a few questions. Were you experiencing any other issues before they did these, for example, there is a high number of refunds, fees charged etc..? Typically you are allowed by law to dispute chargebacks.
I learned from previous experience, never have a single payment processor ever. The best rule of thumb pay the higher fee but diversify.
> Typically you are allowed by law to dispute chargebacks.
One caveat. For online businesses it is very hard to dispute most chargebacks. The card company typically wants you to FAX back a copy of a receipt or invoice for the charge bearing the customer's signature. That's fine for businesses like the OP's, which deals with customers in person, but for most of us who deal with customers via an online shopping cart...nope.
> I learned from previous experience, never have a single payment processor ever.
Note that if you are handling recurring payments then in order to have the flexibility to switch processors you need to either handle credit card storage yourself, or make sure whatever processor vaulting service you use provides a way to export the raw numbers in case you want to switch processors, or use Spreedly or something similar.
We do our own storage where I work. PCI compliance is a bit of work, but it is not as bad as most people think. (If you transaction volume is high enough to not be allowed to the the Self-Assessment Questionnaire, then it is probably as bad as most people think).
Every time it is time to renew the reserved instances at our hosting service that are involved in card storage and would no longer be needed if we used a vault at a processor or a service like Spreedly, we've taken a look at the number of cards we have stored and the transaction volume to figure out the vaulting costs, and so far it has come out cheaper to continue doing it ourselves.
Another issue with using a vaulting service is how to handle expiration dates. The expiration date printed on the card is the date after which the physical card is not supposed to be accepted, not the date that the number itself expires. If you have the card on file for authorized recurring payments, you can continue to charge the account after the physical card expires. But most gateways will reject a transaction at the gateway if the date you supply is in the past. Most gateways have some way to tell them you want to go ahead and try to charge the card even though the expiration date of the physical card is past. You want to make sure that when using such a card from the vault, you can still tell the gateway to try it.
Also make sure that vault works with the card updater services. Visa, MasterCard, and Discover (not sure about AmEx) provide a service whereby a merchant can provide a list of cards the merchant has on file, and the card company will tell them which are still good as is, which have new expire dates but the same number (and give the new date), which have both a new number and date (and give those to you), and which have had their underlying accounts closed.
You have to be able to give the updater service full credit card numbers, so if your cards are in a vault service, you'll have to have the vault service do the updater querying for you.
Location: Los Angeles, CA
Remote: Yes, I have been working remotely for the past 3 years.
Willing to relocate: Yes
Technologies: AWS, Javascript, React, GraphQL, Blockchain, SQL, NodeJS
Résumé/CV: https://drive.google.com/open?id=1M3RDQC8siBpcauFi-TEv48QUWRz9hN3P
Email: ptxdas@gmail.com
just a heads up, your resume is a bit...confusing. Are you looking for a PM position or as an engineer? I think 4 pages is too long as well, I'd try to keep it between 1 and 2 pages.
