#ms.6
1 messages · Page 1 of 1 (latest)
Hi
I can try! what's the question exactly?
I'm making my own custom pages for customers to add card details to their account, for PCI compliance should I be tokenizing the card details in the client side and then linking the token to the customers stripe account in the backend?
I cannot use stripe elements as I am doing a custom design.
yes
Ok
you must use Stripe Elements, that's not really a choice unless your business is PCI certified
you can customise Elements a lot, so I'd work with that.
I am in the process of becoming PCI certified
This is not customizable enough in my opinion, thats why I am using raw card data api.
that seems like a poor reason
really?
becoming PCI certified is a huge lift and cost for your business
did you have specific concerns about specific ways you want to customise Elements? maybe I can find solutions you didn't know about.
I want to use the material input design for the card details e.t.c
Kind of like this :
if you look at the elements-examples link posted above, we have an example that uses floating labels and a link to the repo with the code for it
mybe that's a starting point for customising to your liking
What is a good use case for the raw card data api? if the lack of design flexibility is a poor reason?
being a PCI compliant large company who uses multiple payment processors or 'vaults' your customer's card details yourself, perhaps
if you feel like it's appropriate for you, https://support.stripe.com/questions/enabling-access-to-raw-card-data-apis has all the information on getting permission to submit raw card details; otherwise you must use tokenized solutions like Elements.