#tobewisebeforeiamold_code
1 messages ¡ Page 1 of 1 (latest)
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
đ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1486412330748215487
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
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.
- tobewisebeforeiamold_code, 1 hour ago, 13 messages
- wise_paymentintent-currency, 6 days ago, 21 messages
Hi there
Howdy!
Are you using the flow where you render the Payment Element before creating a PaymentIntent, as in this guide?
Not really. We don't use checkout sessions.
- we create a payment_intent in our API, and get the client secret from that
- Then in the front-end we instantiate an
<Element>from the react-js library component using that secret
Sorry, we use a customer_session secret and a payment_intent client_secret to instantiate the Element
In case it helps, here's a payment_intent ID that I created in our development environment that didn't show PADs: pi_3TEtlpCrxkN8ywNk0mgZDALg
That guide doesn't have anything to do with Checkout Sessions
This one did show PADs pi_3TEtylCrxkN8ywNk19Y0Dyjy
let me see if I can find out why we filtered out ACSS debit on the one
If it is currency amount restrictions then I can't help you and you need to write into support and ask for an increase. Those are specific to the Stripe Account
That guide doesn't have anything to do with Checkout Sessions
Sorry, you're right. I sawimport CheckoutForm from './CheckoutForm';and though it was talking about CheckoutSessions.
So then we don't use mode: 'payment', in the Elements options, and we pass in onChange, onReady, and options into PaymentElement, those options being paymentMethodOrder, layout, fields, terms, and sometimes wallets
If it is currency amount restrictions then I can't help you and you need to write into support and ask for an increase. Those are specific to the Stripe Account
That's OK by me. I really just want to know what the limit is so I can explain behavior to my CEO.
Okay, that's good. ACSS Debit doesn't support the deferred intent flow where you pass mode to the Elements instance
Yeah it looks like your intuition was correct. pi_3TEtlpCrxkN8ywNk0mgZDALg has ACSS filtered out because of the amount. These limits get evaluated/raised over time as you process more on Stripe but you can write into support and see if they can give you an increase and let them know that you're running into limits.
You aren't hitting an API error here because the filtering is happening on the frontend, but you can mention that.
That makes sense. I saw on some site called taxdome that the amount was $3000 CAD. But if I understand you correctly that amount is not a fixed value for everyone, and can be much higher. Is that right? And do you have any indication of what our amount limit is currently?
I think that's right but that's outside the scope of what we handle here and my information is anecdotal.
But my understanding is that support handles these kinds of requests all the time
That also makes sense. That payment_intent I gave you is from a development environment that gets no real customers. So if the value is variable and based on volume then there's probably not much you can tell me from that development payment_intent.
Thank you for your help today! I'll pass that info along to our CEO so that can contact our Stripe rep.
Okay, if you have a real account where you are actively processing ACSS debit payments, then it is fairly likely you're not going to have that issue in livemode