geekypunk

[past ravine]

Hello! No, you should not attach Payment Methods directly to Customers. Is your intent to save these cards for future use, or do you only want/need to charge them a single time?

[brazen glacier]

Hi @past ravine Intent is to save these cards for future use.

[past ravine]

In that case you should use the setup_future_usage parameter on the Payment Intent as described here: https://stripe.com/docs/payments/save-during-payment

[brazen glacier]

@past ravine Yes, I saw that. So we expose a UI in our application for hoteliers to manually key in card details they receive from their guests or from travel portals like Expedia. So there is no payment happening then, just saving a card with the card details. So given that we receive card details(name, number, exp, cvv) as input, how do we store them for future usage, and charge them in future?

[past ravine]

Ah, you want this guide then: https://stripe.com/docs/payments/save-and-reuse

That uses a Setup Intent to save the card for future use without taking a payment now, and explains how to charge them later.

[brazen glacier]

@past ravine I see. Is there a way I can skip Stripe PaymentElement UI elements completely, and just send the card details to an API directly create the SetupIntent. This is because, when we receive their virtual cards, system needs to store/tokenize them automatically for future use. There is no human involved actually entering payment details

[past ravine]

You would need to be fully PCI compliant to do that, because you would be handling raw card details.

[brazen glacier]

@past ravine Yes, we are. How do we submit compliance details to Stripe?

[past ravine]

You would need to talk to support about setting your account up to be able to pass raw card details: https://support.stripe.com/contact/email

[brazen glacier]

Thanks @past ravine. Can customers enter raw card details into the Verifone P400 terminal?