#adam-chargecard-backendonly
1 messages · Page 1 of 1 (latest)
Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- adam-cards-bulkcharge, 1 day ago, 8 messages
When you say "virtual cards" what do you mean? Are there card numbers that can be entered into a UI?
yes these are cards that are only issued for a specific use and don't have a physical card. There are typically one or a few uses with very limited life then they expire. They don't have a customer name. They are issued by all major credit card providers and mainly used between businesses like between hotels and online travel agents to pass payments for reservations
But they do have numbers, expiry, and cvv?
yes they do
And is this something you would be handling through a UI or would this be entirely on the back-end?
ideally entirely through API on the back end
Okay, we have some protections in place to prevent people from passing raw card numbers directly to our servers (our JavaScript library does client-side tokenization) so if you want to pass back the raw details you will need to contact Support to see if we can enable that feature for your use case. https://support.stripe.com/contact
If that is approved you could
- create a Payment Method, providing the card details in the
cardparameter: https://stripe.com/docs/api/payment_methods/create#create_payment_method-card - Charge the saved payment method by specifying the
payment_methodwhen creating the Payment Intent: https://stripe.com/docs/api/payment_intents/create#create_payment_intent-payment_method. You would also passconfirm="True"to skip a second API call for the confirmation.
Alright. Thanks