season0284

[brazen scroll]

hello! When you implement your integration, you would usually use Stripe Elements to collect the payment method details e.g. card number.

If you want to use a Stripe hosted page to accept payment i.e. Checkout Sessions, you can take a look at the quickstart : https://stripe.com/docs/checkout/quickstart

If you want to build your own UI/UX to accept payment, you would typically use what we call the Payment Element, you can take a look at the quickstart here : https://stripe.com/docs/payments/quickstart

[hardy stag]

One of the things I learned in the Custom payment flow tutorial, the value of the paymentMethod field, is what the front-end developer gets. I would like to confirm with you again whether this point I have learned is correct?

[brazen scroll]

what do you mean by the value of the paymentMethod field is what the front-end developer gets? Can you explain in more detail?

[wise forge]


In the test environment, when I simulated the create a paymentIntent and confirm a paymentIntent steps, It is found that when the paymentMethod device in the confirm a paymentIntent interface is set to the corresponding payment method, such as pm_card_visa, the real card number will be displayed on the dashboard platform.

Is the paymentMethod value also used in the test environment for the production environment? Using the values of the test environment, will the dashboard platform actually display the customer's card number at that time?

[wise forge]

Screenshot here

[faint trout]

pm_card_visa is a test payment method that you can only use in test mode

[wise forge]

When in a formal environment, is the value of the payment method field the customer's card number? If not, how can I get the value of this field for the customer who is making a payment?

[faint trout]

What do you mean? you want to get the full card details from Stripe API?

[wise forge]

Not really. I want to know, when using the confirm a paymentIntent interface in a formal environment, what should be passed to the value of the paymentMethod field in order to ensure that the customer can complete the normal payment using the bank card?

[faint trout]

https://stripe.com/docs/payments/save-and-reuse?platform=android&ui=payment-sheet#charge-saved-payment-method are you asking how to create a charge with a saved payment method?

[wise forge]

I don't think so. The background I received is that when expanding overseas, front-end developers will be connected to apple pay products and back-end developers will be connected to Stripe products. In practice, I learned that users would tie their bank cards to apple pay. So I think when backend developers call stripe interface, they should directly use the user's bank card information tied to apple pay. The next question I want to ask is: What value should be passed to the payment method when calling the stripeConfirm a PaymentIntent interface?

[faint trout]

I don't quite understand you, can you rephrase?

[wise forge]

I'm trying to explain to you my current background, is there anything confusing about the background I've described? If not, then I'll explain to you what I don't understand about the payment method field

[faint trout]

Hmm, is it about how to create a payment_method object?

[wise forge]

I think I may not know enough about the official documentation tutorial. In order to meet front-end developers can use apple pay products, back-end developers can use stripe products. Which tutorial document should I refer to? I'm familiarizing myself with the tutorial. I'll come back for advice

[faint trout]

If you are new to Stripe. I'd highly recommend you go through this getting started guide https://stripe.com/docs/payments/accept-a-payment?platform=web&ui=elements

https://stripe.com/docs/payments/accept-a-payment?platform=web&ui=elements#web-create-intent there's a flow chart here to help you understand the key components invovled in a Stripe payment