#meisei81-connect

1 messages · Page 1 of 1 (latest)

molten jacinth
grave token
#

yeah

#

onboard-express-ios-english-french

#

I don't specify country when create an account

molten jacinth
#

hmm, sorry to redirect you but can you write in to Stripe Support with the details so that we can investigate further

grave token
#

ok

#

my second question is how to change phone number in onboarding

molten jacinth
#

that would be a question which Stripe Support would be more familiar with and better be able to help you too

grave token
#

so, my two questions are no answer now?

molten jacinth
#

afaik you cannot change the phone number while onboarding, but you can change your phone number later on the Express Dashboard

grave token
#

stripe-dashboard-change-phone-number

#

I found this from dashboard in test mode.

#

I have write email to stripe support. please have a check.

#

onboard-wrong-phone-number

#

When onboarding, I input the wrong phone number but can't get back to change. Every time I entered the onboarding flow, it shows the sending verification code page.

molten jacinth
#

is this for the same account?

grave token
#

yeah

grave token
#

hello?

grave token
#

you there?

molten jacinth
#

hey, sorry about the delay, i'm not able to replicate the issue

#

for me it doesn't get stuck in the loading page

#

it eventually moves into ^

#

have you tried clearing your cache before accessing a new account link for this account id?

grave token
#

you mean you can get back to change your phone number from this page?

molten jacinth
#

aaaah, alright i get what you mean now

grave token
#

ahah..sorry for my poor english..

molten jacinth
#

@grave token you'd want to reach out to Stripe Support to ask how if it's possible to change a phone number for a new Express account at the onboarding page if you've already keyed in the wrong info initially, I'd strongly recommend providing the steps you took because it took me a while to understand what you meant as well. I'm not sure if this is expected behaviour

#

the workaround would be to create a new account id and have them sign up on a new account instead

grave token
#

for now, our system don't create a new account object for the merchant to re-onboarding

#

because re-use the account id can keep the steps which the merchant has finished.

molten jacinth
#

alright, you'll need to reach out to Stripe Support for us to investigate, it'd take a while

grave token
#

If I create an account for a customer to onboard, and he onboard successfully, then some days pass, I create another account for the same customer to onboard and success. So, is there the latest account belong to the customer? The payment made for the old account would not be seen anymore?

molten jacinth
#

you can't create another account for the same email

grave token
#

I don't specify the email when invoke the create account api

molten jacinth
#

yes, but when the user onboards, they need to input their email and phone number

grave token
#

If so, what should we do if the merchant input the wrong mobile number

#

I just come up the idea that is to create a new account for merchant to re-onboarding

#

but now you say I can't do like that..

#

can you give me a solution..

molten jacinth
#

i believe the new scenario you gave was that the user successfully onboarded right?

#

if the user has already successfully onboarded, why would they have an issue with the wrong mobile number?

grave token
#

If user just in the step after input the verification code, and then they found that the mobile number is wrong, what should we do to fix this problem?

molten jacinth
#

you can create a new account id, and get the user to onboard to that new account -> you can test this out

grave token
#

ok. I'll try it later.

#

I got another question about stripe subscription.

#

Yesterday noon, I had subscripted a daily service in test mode and today noon I had received a customer.subscription.updated event and invoice.created event, but the invoice had not paid at that time. I used to think that the invoice would be paid immediately when the new cycle comes. But actually, it was paid after one hour for that time.

molten jacinth
#

this is expected behaviour, when a subscription renews and creates an invoice, Stripe waits approximately one hour before finalizing the invoice and attempting payment or sending an email.

grave token
#

If the invoice was not paid immediately, we should take the subscription invalid, or we should give some hours for user to use our service and will turn to invalid after hours later.

#

can I set the invoice to be paid immediately?

molten jacinth
#

@grave token i'm going to need to step away for a bit, someone from my team will help you out with your question as soon as they can

grave token
#

ok

west spindle
#

Hey, just catching up!

#

can I set the invoice to be paid immediately?
You can't, no. Not automatically anyway

grave token
#

so, I have to wait one hour for the stripe system to make the invoice paid, right?

#

Usually, before the invoice paid in the one hour interval, how to design the system to deal with the unpaid time? Let the customer to use free for one hour?

west spindle
#

That's generally what most users do before the invoice is marked as past_due (if automatic payment fails)

grave token
#

You mean I should not let the user to use our service before the stripe make the invoice paid, right?

west spindle
#

That's entirely up to you and your business! I personally would rather not have to build and maintain the code to handle that logic

grave token
#

I see..

#

So, from your personal suggestion, I guess that the use can use the service until the stripe tells that the invoice paid failed, right?

west spindle
#

Yes, you could listen for the invoice.payment_failed event