#mexner-paymentelement-acss
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.
@compact crystal What's the question beyond that one link? Please provide a clear summary of your ask and what you need help with
My question is explained here,
#dev-help message
Does that help?
Not really, I'm helping a lot of other people and can't go back and read past conversations. Please try and summarize your question clear here.
ah, ok
using payment elements, I can successfully submit payment elements and create a payment method for CC's. I've now added Canadian ACH as a payment option, and when I try to create a payment method, I'm getting a validation error. The error is too generic and I don't know what is missing since it works for CCs. Any ideas on how I can figure out what information is missing?
"error": {
"code": "incomplete_payment_details",
"type": "validation_error",
"message": "Please provide complete payment details."
}
}```
The support person asked for this request ID to investigate further,
https://dashboard.stripe.com/test/logs/req_8ybRZREBP5Whyl
and here is my code reference,
https://d.pr/i/b3C5Ss
mexner-paymentelement-acss
When you say Canadian ACH you mean ACSS Debit or PAD right? Like https://stripe.com/docs/payments/acss-debit/accept-a-payment?
I don't understand the request you shared. This doesn't come from your own code and is an internal request made by PaymentElement
And the link is a picture of code so I also can't do much with this
Are you using the deferred intent flow where you collect payment method details first and then later create the PaymentIntent?
If so, ACSS Debit is not supported with that flow
Ah... Yes I am using deferred payment intent and realize ACSS Debit is not supported. I am now trying to rebuild our integration to not use deferred intent - so that we can support ACSS Debit.
console.log("loaderror!!!! ", event);
});```
add this to your code, if you do you'd see the error on load
sweet - i'll do that now. thank you!
btw - is there anything i can do to prevent a thread from auto closing? Or is that just the way it is?
That's the way it is. We help in real time here. There are dozens of people who ask for help a day. So it's not a long running private support chat for yourself.
If you want that approach, the best option is to talk to our support team instead: https://support.stripe.com/contact
makes sense, thanks!
sure thing!
It's totally fine to ask us new questions in #dev-help, just make sure you're clear about your overall question so that it's all self contained! And try to engage in real time with us here (like you're doing now) when asking for help as we can't just keep threads open for multiple hours waiting
👍
Do you have any other questions?
will this create a request Id in stripe?
elements,
params: {
billing_details: {
name: name,
address: {
postal_code: postal,
country: country
},
email: email
}
},
})```
this is what is throwing me the generic error "incomplete_payment_details"
And... is there another help article that explains how to undo deferred intent? I have followed and implemented this, and am trying to undo this. But I don't see what the "normal" approach is.
https://stripe.com/docs/payments/accept-a-payment-deferred
When you call createPaymentMethod, it's going to call our Create PaymentMethod API https://stripe.com/docs/api/payment_methods/create. But here nothing happens because you are tring to create a PaymentMethod with PaymentElement that is crashed. Like I assume you noticed on the screen nothing appears, you never enter ACSS Debit details or anything like this, so it's normal this is failing
yep - 100%, but I can't figure out why.
I just explained why already I thought we were aligned
b/c of deferred intent?
ACSS Debit is not supported in PaymentElement with the deferred flow. So if you try to initialize PaymentElement for ACSS Debit, it will fail, so you get a loaderror which you weren't handling, and then instead of realizing "oh there's no ACSS Debit detials to enter something is wrong" you just confirmed and called createPaymentMethod() which errors saying "well we have no payment method details at all, something is missing, please investigate"
Does that part make sense?
Yes.
Okay so that's why the error is a bit vague. IT's because it's purely a dev error. So really if you use the deferred flow (which is fine to use) then you just can't use ACSS
yep - i'm trying to learn how to undo deferred flow
ACSS Debit is extremely hard to use because that payment method comes with extremely strict rules around mandate collection for example and you have to provide a lot of information upfront on the PaymentIntent creation. My advice is to just not bother with ACSS if you want to use the Deferred flow which seems to work for you already
yea - I'm on the same page as you; but our company is expanding into Canadian territory and I have to learn how to support ACSS. And I realize it's a lot of work to implement.
I think a good question to help me reframe all of this is, how do I undo deferred intent?
I just don't have context of how to implement outside of deferred intent. Is there a support page showing a "normal" way?
I've been looking all around the left hand links on this page,
https://stripe.com/docs/payments/accept-a-payment-deferred
https://stripe.com/docs/payments/accept-a-payment this is the canonical integration path. And https://stripe.com/docs/payments/acss-debit/accept-a-payment follows the same flow
you basically have to flip the order over completely
- Create the PaymentIntent server-side and get a
client_secret - Render PayemntElement client-side