#jayvir_api

1 messages · Page 1 of 1 (latest)

sly starBOT
#

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

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

foggy stream
#

link integration with stripe card is already implemented

const setupIntent = await stripe.setupIntents.create({
  usage: 'on_session',
  customer: customerInfo.id,
  automatic_payment_methods: { enabled: true },
});

link is not showing in UI

just card is showing

thick oak
#

👋 happy to help

#

would you mind sharing a link to your testing site?

foggy stream
#

i am testing in localhost FYI

thick oak
#

ok what's the SetupIntent ID?

foggy stream
#

seti_1RMqIFLKTM2K3idylsjgkbQJ

#

another id :
,
seti_1RMqJRLKTM2K3idyO8pSgUCb

thick oak
#

will take a look and get back to you in a sec

#

the secret actually doesn't matter

#

would you mind removing it please

foggy stream
#

i have on in my connected account

#

we use platform + connected stripe flow

#

stripe.paymentLinks.create() - show but

const setupIntent = await stripe.setupIntents.create({
usage: 'on_session',
customer: customerInfo.id,
automatic_payment_methods: { enabled: true },
});

doesnt show what i am doing wrong

thick oak
#

sorry I still haven't had the time to take a look

#

please give me a moment

#

just fyi both of these SetupIntents are created on your platform

#

and not on a connected account

#

and link is not compatible with "on_session" usage

#

it's only available for off_session

foggy stream
#

i made off_session as well - seti_1RMqTYLKTM2K3idyK1ssxmrU

still not showing link

thick oak
#

Link is not supported for India customers

foggy stream
#

we dont use for india
we use for us

thick oak
#

but you are in India right?

foggy stream
#

yes ur right
how to test ?

thick oak
#

someone from the US needs to test

#

or any other country

sly starBOT
foggy stream
#

@thick oak @lament snow
cant i test with browser country change example san fransico in chrome
so i can test link

#

it is not working still

#

please guide me

lament snow
#

Hey there, possibly, though we use IP address and other indicators to detect country, so this may still not work

#

You really need to test from a device not based in India

foggy stream
#

oh damn @lament snow

lament snow
#

I would suggest using a remote device, either one you own elsewhere or a service like BrowserStack with devices based in other geographies

foggy stream
#

let me summarize for link integration to work ?

const setupIntent = await stripe.setupIntents.create({
usage: 'on_session',
customer: customerInfo.id,
automatic_payment_methods: { enabled: true },
});

changes
for link i have usage off_session
test from another country

right ?

#

@lament snow

lament snow
#

Correct, Link does not support on_session mandates, if the customer is on session they should authenticate the Link payment each time

#

See here: https://docs.stripe.com/payments/wallets#api-support

1 Cards and bank debit methods including SEPA debit, AU BECS direct debit, and ACSS debit support both on_session and off_session with setup future usage. All other payment method types either don’t support setup_future_usage or only support off_session.

foggy stream
#

@lament snow

Something went wrong
Your account can’t be connected at this time. Please try again later

#

what us number to enter for testing - link integration?

#

@lament snow

lament snow
#

You should be able to sing up with any email and fake phone in test mode, then authenticate with the test 000000 OTP

foggy stream
#

Something went wrong
Your account can’t be connected at this time. Please try again later.

#

@lament snow why i am getting this error ?

lament snow
#

I don't know -- where are you encountering it and what are you doing? Can you share a test page and steps where i can reproduce?

foggy stream
#

@lament snow work fine now
i made mistake in email

#

thanks @lament snow issue solve as of now

lament snow
#

Great! Happy to help 🙂