#raghul-s_api

1 messages · Page 1 of 1 (latest)

zinc pathBOT
#

👋 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/1309043865663049789

📝 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.

forest pier
#

hello! gimme a while to take a look

forest pier
#

did this work previously?

heady token
#

iDeal wasn't visible previously for recurring products. Now, We enabled iDeal for recurring payments in Billing Payments config of connected account. And it's visible for the customers!! And the payment doesn't go through for recurring product payment

And I want to understand how does the specificity work between payment method configuration of the connected account's billing payment config vs LeadConnector's payment method configuration which we use in the payment element

forest pier
#

I expect iDEAL to also be available as a payment method option for Subscriptions, but it's not showing up now. As far as I can telll, this doesn't have anything to do with the PMC .

I'm going to share a link with you, can you create a support ticket via that link and I'll get back to you

zinc pathBOT
#

Please click this link to open a support case with our Developer Support team, in order to help you more effectively.

Here's what to expect:

  • 🧑‍💻 You may need to log in to your Stripe account first.
  • ☑️ You'll be asked to confirm that you want to create a support case.
  • 🔗 Your case will be routed to our Developer Support team and they will have a link to this Discord thread to preserve context on your question.
  • 📩 The team will review your question and reply to your support case as soon as possible.

Why can't you answer right now?

  • ⏱️ Sometimes answering technical/developer focused questions can take some time to reproduce problems or dig into edge cases or your specific account setup to get you the best possible answer, and it's not always possible to do this live in Discord.
heady token
#

Because, we thought the LeadConnector's payment method configuration which we use in the payment element would override any other configs. But here, we have another case where Amazon pay enabled in LeadConnector's payment method configuration but disabled in Billing payment config which doesn't show Amazon pay in the payment element

forest pier
#

I understand. Create a support ticket via that link and I'll get back to you on the ticket

heady token
#

I created one

forest pier
#

yep, i see it, thank you!

heady token
#

I have a question, while displaying payment methods in payment element, don't we consider the PMC we pass in? Or the payment methods will always be displayed only based on the connect account's billing payments config?

#

Because, we thought the LeadConnector's payment method configuration which we use in the payment element would override any other configs. But here, we have another case where Amazon pay enabled in LeadConnector's payment method configuration but disabled in Billing payment config which doesn't show Amazon pay in the payment element

Here's Amazon pay wasn't visible only for Recurring product payments

forest pier
#

can you share the specific PaymentIntent id for the above case with Amazon Pay?

heady token
#

Sure. Give me 2 mins. I'll share you the checkout session cURL for the case

#

In this case,
We pass in LeadConnector's PMC ID for the checkout where the AmazonPay was enabled
AmazonPay was disabled in connected account's Billing payments configuration

cURL:
curl 'https://api.stripe.com/v1/elements/sessions?deferred_intent\[mode\]=subscription&deferred_intent\[amount\]=22000&deferred_intent\[currency\]=usd&deferred_intent\[setup_future_usage\]=off_session&deferred_intent\[payment_method_configuration\]\[id\]=pmc_1M95aRFpU9DlKp7ReIqqY0PP&key=pk_test_WvH5LGch2F7bqyIJ6gVMu3iE&_stripe_account=acct_1Ihw53CScnf89tZo&type=deferred_intent&locale=en-GB&referrer_host=stripe-pmc-dot-funnel-preview-dot-highlevel-staging.uc.r.appspot.com&session_id=elements_session_1sk1M3Um4O6&stripe_js_id=ff5ef0c1-bc3c-4ea9-9b66-da68a09c75c7'
-H 'accept: application/json'
-H 'accept-language: en-GB,en-US;q=0.9,en;q=0.8'
-H 'content-type: application/x-www-form-urlencoded'
-H 'origin: https://js.stripe.com'
-H 'priority: u=1, i'
-H 'referer: https://js.stripe.com/'
-H 'sec-ch-ua: "Google Chrome";v="131", "Chromium";v="131", "Not_A Brand";v="24"'
-H 'sec-ch-ua-mobile: ?0'
-H 'sec-ch-ua-platform: "macOS"'
-H 'sec-fetch-dest: empty'
-H 'sec-fetch-mode: cors'
-H 'sec-fetch-site: same-site'
-H 'user-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36'

Note: Now, we have enabled back the Amazon pay in connected account's Billing payments configuration as our team is working on something

forest pier
#

what's the request id for the above request?

#

also, how did you get the above command? This isn't a request which you should be running via cURL. It's typically a request made by the Payment Element itself

heady token
#

Yeah, I was explaining about the Payment element.
Amazon pay wasn't visible only for Subscription mode

#

This issue I was explaining second was not on a payment. It's in the checkout. Amazonpay wasn't visible in checkout where Amazon pay enabled in LeadConnector's payment method configuration but disabled in Billing payment config.

This is where I was asking
while displaying payment methods in payment element, don't we consider the PMC we pass in? Or the payment methods will always be displayed only based on the connect account's billing payments config?

forest pier
#

okay, let's take a step back, the reason why I'm asking how did you get that command, and also why I'm asking for the request id is that the request which you shared with me shouldn't have been successful

#

logically, if you're using the stripeAccount header, the PMC which you pass in should belong to that of the stripeAccount. It's pretty unexpected to me, that you can pass in the platform's PMC, include a stripeAccount without it errorring

#

now, briefly returning to your original question about iDEAL, i can't replicate what you mentioned happened. Can you share your code snippets for how you did it? Were you also explicitly passing in a PMC?

heady token
#

okay. Let me get back to you with the code

#

You mean, we shouldn't use platform account's PMC for connect account's checkout request?
We do it this way because we have to display specific payment methods for the checkout as we have multiple checkouts in our app. Each set of customers will use specific payment methods which they are allowed to pay with

forest pier
#

before we move on with anything, can you share the corresponding request id for this so that I can take a look at how your account works first?

https://api.stripe.com/v1/elements/sessions?deferred_intent\[mode\]=subscription&deferred_intent\[amount\]=22000&deferred_intent\[currency\]=usd&deferred_intent\[setup_future_usage\]=off_session&deferred_intent\[payment_method_configuration\]\[id\]=pmc_1M95aRFpU9DlKp7ReIqqY0PP&key=pk_test_WvH5LGch2F7bqyIJ6gVMu3iE&_stripe_account=acct_1Ihw53CScnf89tZo&type=deferred_intent&locale=en-GB&referrer_host=stripe-pmc-dot-funnel-preview-dot-highlevel-staging.uc.r.appspot.com&session_id=elements_session_1sk1M3Um4O6&stripe_js_id=ff5ef0c1-bc3c-4ea9-9b66-da68a09c75c7'
#

I assume you were testing it on the spot, the request id should be able to be found in the header

#

or if you have an existing site where you're testing this flow out, can you share that with me so that I can take a look?

heady token
forest pier
#

alright, thanks! gimme a while to take a look

heady token
#

Whenever you select a product, checkout sessions API will call displaying payment methods in payment element. Right now, Amazon pay is enabled in connected account's Billing payments configuration & also LeadConnector's payment method configuration

So, it's visible for recurring products.

zinc pathBOT
tacit sparrow
#

👋 taking over for my colleague. Let me catch up.

#

@heady token since we already have an opened case would you mind replying to the email with a more detailed explanation of your issue. We will have to investigate it async and we will reply to you soon

heady token
#

Can you please answer the question below

while displaying payment methods in payment element, don't we consider the PMC we pass in? Or the payment methods will always be displayed only based on the connect account's billing payments config?

tacit sparrow
#

it depends on how you're initializing your Stripe instance in the frontend

#

whether you pass in the StripeAccount header or not

heady token
#

We use deferred intent flow & we pass in below options
{
mode,
amount,
currency,
captureMethod,
payment_method_configuration
}

tacit sparrow
#

when you create the const stripe = Stripe... do you pass your connected Account Id?

heady token
#

yes, we do

const stripe = await loadStripe(publishableKey, {
stripeAccount: accountId || undefined,
})

heady token
#

@tacit sparrow there?

tacit sparrow
#

sorry for the late reply

#

@Raghul S since we already have an opened case would you mind replying to the email with a more detailed explanation of your issue. We will have to investigate it async and we will reply to you soon
@heady token I honestly think in your case it's better to assist you async since the investigation needs a lot more time than we can accord you while also replying to everyone else on discord