#softnet-paymentintent-newpaymentmethod
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.
- venkateshjsoft, 3 hours ago, 22 messages
- venkateshjsoft, 3 days ago, 10 messages
- venkateshjsoft, 3 days ago, 2 messages
๐
Hi
pi_3ObQ6MB4yD6nPBkB19DlsfGU
I'm testing a scenario to collect money from the user second time.
I want this second payment failed so I can try my changes to update the payment intent
is this possible?
You could block it with a Radar rule
Otherwise the best thing to do is just mock a failed response for your test
Ah this is a SEPA Debit
So Radar won't work
Yeah so best thing to do is to test out failure with a PaymentMethod that fails
Then mock the response here with that same response
okay sure
let me try
i try to give some random payment method but it is not creating payment intent itself
Not sure what you mean by that
See the test IBANs here: https://stripe.com/docs/payments/sepa-debit/accept-a-payment?platform=web&ui=checkout#test-ibans
You want to use one of the ones that transitions to requires_payment_method
That means there was an async failure after confirmation
this is my first payment request req_P7tZKaVBHcv3MA
this is my second payment request req_Z1Lr7xMi6VVLRI
first time i using ideal payment to make the payment
this payment method is then changed to sepa debit as ideal is not supported for future payments
is this clear?
Sure
But for this test you want to create/confirm a PaymentIntent using one of those other SEPA IBANs
That fails
Not with iDEAL
Just so you can see what the response looks like
okay I will try
In terms of the charge.failed Event
I have another question
Sure
{
"id": "pi_3ObQ6MB4yD6nPBkB19DlsfGU",
"object": "payment_intent",
"last_payment_error": null,
"livemode": false,
"next_action": null,
"status": "requires_payment_method",
"amount": 5800,
"amount_capturable": 0,
"amount_details": {
"tip": {
}
},
"amount_received": 0,
"application": null,
"application_fee_amount": null,
"automatic_payment_methods": null,
"canceled_at": null,
"cancellation_reason": null,
"capture_method": "automatic",
"client_secret": "pi_3ObQ6MB4yD6nPBkB19DlsfGU_secret_Wtk5r1EmyYjz7cAchxBZkz4Jg",
"confirmation_method": "automatic",
"created": 1705939918,
"currency": "eur",
"customer": "cus_PQGbHtnkRwVLii",
"description": null,
"invoice": null,
"latest_charge": null,
"metadata": {
"InvoiceId": "",
"OriginalPaymentIntentId": "pi_3ObQ4lB4yD6nPBkB1XHJcY4J"
},
"on_behalf_of": null,
"payment_method": null,
"payment_method_configuration_details": null,
"payment_method_options": {
"sepa_debit": {
}
},
"payment_method_types": [
"sepa_debit"
],
"processing": null,
"receipt_email": null,
"review": null,
"setup_future_usage": null,
"shipping": null,
"source": null,
"statement_descriptor": null,
"statement_descriptor_suffix": null,
"transfer_data": null,
"transfer_group": null
}
this is my sample request
for me this request works fine in local but its failing in production
I want to know if its possible to change this payment intent to allow other payment methods
Can you share a request ID for whatever is failing in production?
And yes, you can re-confirm that PaymentIntent with a different PaymentMethod if you want
Ah that is failing in production for a different reason
You can see that that Bank Account has been flagged for a high likelihood of chargeback
Meaning it is likely fraudulent
But you can still re-confirm that PaymentIntent using a different PaymentMethod
we recently migrated to Stripe from day 1, none of the payments with Seba debit is working
we discoverred this recently
Hi ๐
I'm stepping in for my colleague and catching up. There is a lot of back and forth in this thread. Can you clarify what your current question is?
There are 2 issues here
first one, I want to know if i can change/add more payment methods to the existing payment intent which was failed
- Yes, you can swap out the Payment Methods used to confirm a Payment Intent if the first confirmation failed
confirmpaym
so in the confirmpayment I can just pass the payment intent and payment methods then it will start accepting new payment methods correct?
Sorry that isn't at all clear
it will not change the exisiting payment failed to successed or different status right?
In the Confirm API request you would pass the ID of the Payment Intent and the ID of the new payment method
can you plz share sample request for this
The Payment Intent will change but the previous Charge will still be a failed charge
IT's literally the /confirm request we document here: https://stripe.com/docs/api/payment_intents/confirm
You just pass in the ID of the payment method when you make it
I can also pass multiple payment methods right?
No
PaymentMethodTypes
In what API request would you do this?
the first payment is failing, now I want to give ablity to the user to choose any payment method (seba, ideal, card)
first payment is failing because of some reason and I dunno what will be the user's preferred payment method, so I want to give them the option to choose
is this clear?
ARe you confirming from the client-side or the server-side?
server side
Basically. yes you can pass multiple values for payment_method_types parameter when confirming. However, what is confusing me, is that your code should know the type of the payment method already since you have to provide the ID.
https://stripe.com/docs/api/payment_intents/confirm#confirm_payment_intent-payment_method_types
let me explain again
we try to collect payment from the user but for some reason the payment is failing on Stripe
we want to give the ablity to the user to choose different payment method so they can choose card, ideal to continue payment
currently we are showing one option which is also not working
cleaR?
No, not really.
How is your integration choosing to display saved payment methods?
For the first time payment in the UI, we give all the payment option to the user to choose.
for the second payment we try to get the payment method which user used before and collect payment without user intervention
since ideal is not supported for future payments, we collect money as seba debit
but this is not working at the moment due to some reasons.
now we want to send an email for the user to choose payment method of their choice
so I want to change the existing payment intent which was failed to support other payment methods
Okay. So you can update the Payment Intent to accept other Payment Method Types.
okay then I dont need to use confirmpayment intent right?
You have to confirm the payment intent
im confused
You explained plenty of reasons why you are doing something but can you please explain what you want to do in terms of API calls
e.g.
- Create Payment Intent
- Attempt confirmation <- charge fails
...
What are the steps you want to take?
- Create payment intent.
- Charge failed
- I want to update payment intent to include extra payment methods (ideal, card etc)
- Once this is done, I will ask the user to choose different payment method to confirm the payment.
Okay so
3. Use the Update API to allow more payment method types (ideal, card, etc.) https://stripe.com/docs/api/payment_intents/update#update_payment_intent-payment_method_types
4. Confirm the payment intent using the ID of the new Payment Method the customer has selected https://stripe.com/docs/api/payment_intents/confirm#confirm_payment_intent-payment_method
great its clear
Thanks
lets go to my second issue
in our production all seba-debit payments are failed by Stripe
blocked by stripe
we dont know the exact reason for this
I can't help with that.
You will ned to reach out to Support
https://support.stripe.com/contact
sure, Thanks