#Jeremy T.

1 messages · Page 1 of 1 (latest)

true socketBOT
quaint cosmos
#

hello! can you share more on why you're doing this i.e. just getting the card details then discarding the created payment method?

marsh fiber
#

Sure. On our mobile app, we have a requirement where we show different dialogs/screens depending on the card's brand and its funding before we associate the card to the customer/user.

quaint cosmos
#

can you illustrate this with an example perhaps?

#

I'd like to know what would the dialog / screen say e.g. for a specific card brand and funding?

marsh fiber
#

We have different texts and flow depending on if it's a Visa Credit card or MasterCard.

quaint cosmos
#

for context, i strongly discourage doing this because :

  1. yes, there are rate limits : 100/rps - https://stripe.com/docs/rate-limits
  2. Collecting the raw credit card numbers in your custom form and then using the Stripe API directly to tokenize the cards subjects you to the full PCI compliance standards. In your case this means you’d have to submit a SAQ D form annually to prove that you are PCI compliant. It’s a 40 page form and not a headache most people want to be dealing with — see https://stripe.com/docs/security/guide#validating-pci-compliance under "API Direct"
marsh fiber
quaint cosmos
#

yes it does