#User1-PI
1 messages · Page 1 of 1 (latest)
Hi! What is the "transaction ID"? The PaymentIntent ID, or some metadata you added to the PaymentIntent, or something else?
transaction id means the completion of payment reference like we are using that i the future like refund or any payment related query. i think i will consider the payment_intent id as transaction id right?
also i have some other question if the confirm payment is failed due to some other reasons. how the incomplete payment intent will act? its not considered as successfull payment and not added in the payout right?
If you want to retreive the PaymentIntent ID, you have two options (as I mentioend in the previous thread):
- Listen ot webhook events, like
payment_intent.succeeded - On the frontend with https://stripe.com/docs/payments/payment-intents/verifying-status#checking-status-retrieve
how the incomplete payment intent will act?
Then users won't be redirected to thereturn_url. And you can check for the error in theconfirmPaymentcall as shown here: https://stripe.com/docs/payments/accept-a-payment?platform=web&ui=elements#web-submit-payment
yes but how the transaction will considered. because i see the dashboard the payment will show incomplete status. its fairly acceptable or not. because if the paymentintent failure and user try to reattempt to pay we have to create new payment_intent and proceed the order. but the incomplete payment will remain same.
Yes, that's expected. PaymentIntent don't expire, so the incomplete PaymentIntent will stay. If you want to cancel the incomplete PaymentIntent, you can do that manually with https://stripe.com/docs/api/payment_intents/cancel?lang=node but you don't have to.
also another doubt. how we can perform saved card functionality in stripe js with payment_intent.
in our current charges integration we create a customer and attached token with customer and using default-source method to accive this.
but now how to we handle this? is stripe js displays saved cards?
So you want to create a PaymentIntent and save the card at the same time? Then use setup_future_usage https://stripe.com/docs/api/payment_intents/create?lang=node#create_payment_intent-setup_future_usage
Actually we have this process in the current integration. so we expect the same in migration as well.
- we have collect the card details from our UI
- we provide an option save card check box to user
- once they selected save card option we will create
stripe_customerand attached card token to customer. - so next time that customer came to order we will list the cards, once they select the card we will make payment using
make_default_resourceandchargesapi.
so basically we want saved the card, and list the card and then if they choose some card then we will debit the amount on selected card
Yes that should work. To save the card we recommend using a SetupIntent, or a PaymentIntent with setup_future_usage. Both of these options will attach the payment method to the customer.
And you can list the payment methods of a specific customer with https://stripe.com/docs/api/payment_methods/list
Stripe JS have an option to list the saved card? or we will implement our own UI to list the card?
You will need your own UI for this.
if we need our own UI, we will do all the things via API only. becuase in the normal flow when we create payment_intent then use stripe js comfirmpayment function to complete the payment.
if we use our UI for saved card purpose and normal flow will use stripe js UI it will misunderstand for users(because the card info page itselef we have to provide option for save card for future checkbox). and also if we using our UI to collect card information it will applicable for SCA?
i am confused how we can manage all the existing thing during this payment_intent migration
if i am using our own UI for saved card purpose then why we need stripe js for normal flow. we can use our own ui for now payment flow also? but i dont know how to we confirm the payment_intent by using API's
did you able to see my previous conversation with soma? or can i ask my question again?
There's a lot to parse, can you summarise the ask?
actually i am ask how to perform saved card via stripe js. we need to list the saved card .but soma said if you need the card list you can implement your own UI
if we need our own UI, we will do all the things via API only. becuase in the normal flow when we create payment_intent then use stripe js comfirmpayment function to complete the payment.
if we use our UI for saved card purpose and normal flow will use stripe js UI it will misunderstand for users(because the card info page itselef we have to provide option for save card for future checkbox). and also if we using our UI to collect card information it will applicable for SCA?
i am confused how we can manage all the existing thing during this payment_intent migration
if i am using our own UI for saved card purpose then why we need stripe js for normal flow. we can use our own ui for now payment flow also? but i dont know how to we confirm the payment_intent by using API's
if we use our UI for saved card purpose and normal flow will use stripe js UI it will misunderstand for users(because the card info page itselef we have to provide option for save card for future checkbox). and also if we using our UI to collect card information it will applicable for SCA?
Yes, your payments will still likely fall under SCA regulations
i am confused how we can manage all the existing thing during this payment_intent migration
if i am using our own UI for saved card purpose then why we need stripe js for normal flow. we can use our own ui for now payment flow also? but i dont know how to we confirm the payment_intent by using API's
You need Stripe.js to handle 3DS challenge flows. That can't be done via the API
can i use payment_intent without stripe js? and it will fall under SCA regulations?
if ues please share the procedure
I don't understand the Q
actually our main goal is need SCA(we already using charges api integration with saved cards). so that we migrate to payment_intent .but if we use stripe js the saved card is not available so we need own UI for saved card.
so that is it possibe to use own ui(collect card info) with payment_intent? its fall under SCA?
but if we use stripe js the saved card is not available so we need own UI for saved card.
Well, this isn't entirely true. You'd build your own UI to present the saved cards, and then pass thepm_xxxID of the selected card to Stripe.js when confirming: https://stripe.com/docs/js/payment_intents/confirm_card_payment#stripe_confirm_card_payment-existing
is this possible to use payment_intent without stripe js.delaing only backed API's?
Hi 👋 stepping in as my teammate needed to step away. You won't be able to build an SCA-compatible flow without a frontend that your customers would interact with for the authentication challenge.