#stripe

@ywain in the API, i cant find the invoice number? is the ID is the invoice number?

zeros: are you talking about the number that appears on the email receipt? or just the invoice IDs that are visible in the dashboard?

@ywain in the email receipt; yes; is that the invoice number?

zeros: you can get the receipt number via the `receipt_number` attribute on the charge object: https://stripe.com/docs/api#charge_object-recei.... Note that this attribute is only populated once an email receipt has been sent.

ywain: how do i get the invoice number?

zeros: the invoice ID ("in_" followed by random alphanumeric characters) is accessible via the `id` attribute on invoice objects (https://stripe.com/docs/api#invoice_object-id)

ywain thanks

hello

payment with bitcoin takes how long to process? and asynchronous as well as the card?

igor_skiter: card payments are synchronous. For Bitcoin, once the customer has pushed the funds to the Bitcoin address and the Bitcoin source has become `chargeable`, creating the charge should succeed immediately

cf. https://stripe.com/docs/sources/bitcoin#charge-...

after creating a 3d secure source, if the status is immediatly set to "chargeable" : can it be directly used to subscribe a customer to a plan (without doint 3d secure verification) - also what can happen if even with this status i redirect the user to 3d secure verification page ? (does it will fails ?)

How much more or less can this take?

Hi kslimani. No, even if the source's status is immediately set to `chargeable`, 3DS sources are still single-use so you cannot use them as a customer's default source for a subscription. You'd still need to set the _card_ source as the default source, create the first payment manually using the 3DS source and create the subscription with a trial period to bypass the first payment, as explained in https://stripe.com/docs/sources/three-d-secure/...

ons

sorry, link got truncated. https://stripe.com/docs/sources/three-d-secure/...

if the source's status is immediately `chargeable`, the `redirect[url]` attribute will be null so you would not be able to redirect the customer

igor_skiter: for the source to become chargeable? as long as it takes for the transaction to appear on the blockchain. can be a few minutes to a few days depending on the transaction fee

ok i see, so i must handle this particular case. thank you

:/

kslimani: yes, you should definitely check whether the source is `pending`, `chargeable` or `failed` after creating it, as all 3 are possible

igor_skiter: that's just how Bitcoin works unfortunately. You can use webhooks to process the payment asynchronously and let your customer know (e.g. via email) if the transaction succeeded or not

will do, also maybe add in documentation that redirect is null if status is chargeable (i don't see this info in doc)

i think it'san important point

kslimani: I guess it's implied, but I'll share your feedback with the docs team

ywain: in the particular case that source is immediatly chargeable (and redirect is null) does the 'source.chargeable' webhook event is triggered ?

kslimani: yes

ok so it is the same event as it would happen after a successfull 3D secure verification ?

hey Stripe support :-)

Ola!

kslimani: yep

We are using connect and want to only get connected account customers to connect once. We also need to test. Can this be done? Should we connect on live and then use the same details in test mode?

ywain: perfect, thank you

Dubs: are you using Standard accounts?

hmm, not sure actually - how can I tell?

all the connected accounts are standard, according to the connected accounts overview page

Dubs: there are three types of accounts that be used with Connect: Standard, Express or Custom. The differences are explained here: https://stripe.com/docs/connect/accounts

We'll be standard then

Dubs: ah, okay, thanks. Can you clarify what you mean exactly by "[we] want to only get connected account customers to connect once"? Do you want to prevent users who were disconnected from your platform from reconnecting?

No - sorry

What I mean is do we have to connect customers for test and live, or can we do it once for both?

Dubs: Ah, gotcha, thanks for the clarification. If an account is connected in live mode (i.e. using your production client_id), your platform will be able to issue both live and test API requests on behalf of this account. However, if the account is connected in test mode (i.e. using your development client_id) then your platform will only be able to issue test API requests on behalf of this account, and you'd need to have the account go through the

OAuth flow again (using your production client_id) in order to connect it in live mode

okay - great. Thanks for clarifying that :-)

Next question - we have a bunch of connected accounts on the platform - can I query the additional parameters you get back from the oauth callback or will they need to connect again? i.e. if I have their account numbers can I get from the API things like TokenType, PublishableKey, AccessToken, etc. from the connected account?

In testing we didn't save these parameters - only the account number and realise we should have saved these extra details too

Dubs: you cannot, but you don't need them. The only important information is the account's ID. With the account ID you can issue any API request on behalf of the account using your own API key and the account's ID in the `Stripe-Account` header (https://stripe.com/docs/connect/authentication#...). The other parameters are mostly there for compliance with the OAuth protocol and compatibility with older integrations

ah, okay. That's great. Thanks so much for your help :-)

np! :)

Trying to test payment request button in safari 11 on macbook pro Sierra. I have a payment method set, but canMakePayments returns null

It works great in Chrome on my PC showing the Android Pay button . . . my client requested ApplePay specifically so I need to test it out.

Any suggestions?

Hello hello

where exactly customer is saved?

with key is for the customer card?

I opened up the Safari settings > autofill and added my card info there

Is that what you mean?"

sorry stripes . . . I thought you were answering my question with a question LOL

@stripes the customer should get saved on stripe so you can load them up later

if you need to get their card info you first load the customer and then load the card with the key

Hi @dawoodman71: in the case of Safari 11 on Sierra, the requirement for Apple Pay would apply: https://stripe.com/docs/stripe-js/elements/paym...

@stripes: indeed when creating a customer using https://stripe.com/docs/api#create_customer the customer object will be saved on Stripe's end

@psmvac I have registered the domain with ApplePay on stripe . . . did this when testing on PC Chrome so I know that's working. Do I need to do something more on Safari to provide the payment method?

@dawoodman71: when using the payment request button and testing with PC Chrome, I believe Chrome's saved card payment sheet would be shown and not apple pay. Domain verification steps would be applicable only in the case of apple pay. Since you are testing on Safari on a mac, do you have an iPhone with a card in its wallet paired to your mac ?

@psmvac No I do not. I have an Apple ID set up with a card, but I'm guessing that's just for the iStore and not ApplePay

Hey Guys, I do have a question concerning the connection between stripe and shopify ? Is there a way to register my client in stripe through the Shopify checkout process ?

@pcmvac I had hoped that adding the autofill to Safari was sufficient (as in Chrome), but I should have known it would be more difficult with Apple :)

Hello, quick question about stripe connect destinations. Can you send one payment with multiple destinations with different amounts? So the customers card only gets charged once?

@dawoodman71: If you want to test with Safari on Mac you would need to have an iPhone paired to meet the requirements.

@pcmvac thanks for your help. Now I just have to find an iphone to test with.

@dawoodman71: haha :). Saved cards would be applicable to Chrome (Desktop or mobile), in the case of Apple Pay it would have different requirements

You could also use the Simulator and visit the page with Safari within the simulator

Hey folks - i'm doing the standard oauth flow and am getting this error: " {"error":{"message":"Cannot switch to an account that the user is not an admin of"}}". Any idea what that means or why its coming up?

Aaah . . . the simulator!

I'll check that out.

@Russell: You could make the charge on behalf of the connected account and then transfer the funds as needed to different connected accounts: https://stripe.com/docs/connect/charges-transfers

What's the deal with creating orders in the system? I take orders on my site and push the charges to stripe. I want to push an order to stripe as well, but I need to be able to specify tax (in NJ only) and shipping (intl only) but it won't let me add items of type tax or shipping. If I set tax on my account it's going to want to charge tax everywhere. Should I just make a SKU for shipping and tax?

@psmvac thank you, will take a look

@jonesdawg: when you tested the flow did you tested it in the same browser that you used for your own Stripe session ?

i need help activating my account

psmvac If I open a fresh window, no cookies, the page loads/functions perfectly. But if I'm signed into a Stripe account (not the platform account) I get this error. I also get it if I click sign in on the Oauth page and try to go the oAuth URL again

Hi @Arjan_: we can't help with account-specific issues here, but our support should definitely be able to help you with this: https://support.stripe.com/email

@psmvac if we go the route of transferring the money ourselves does the money ever hit the connect accounts owners account? One reason they like the destination approach is the funds never hit thier bank account so it makes thier accounting eaiser

I see you can set "source_transaction"

which will connect the transfer to the charge, will that ensure the funds are transferred before it is paid out to the stripe owners account

*bank account

Russell: I believe that you are correct.

thank you @ftknox

Hello everyone, got a question about stripe webhook

it happened yesterday that the same event was sent out twice

for source.chargeable

is this something that I should protect from? Never seen that happen before

karol_rybak: That is odd. Did your webhook handler not respond to the first instance of that Event with a 2XX status code?

well not 100% sure but I didn't see any errors in log

there's about an hour difference between each call

is there a way to check that on dashboard

karol_rybak: that makes sense then since Stripe will retry about once an hour if a Webhook fails to receive a 2XX response

karol_rybak: You should be able to search for the Event id in your Dashboard and see the status of each Webhook attempt at the bottom of the resulting page

I probably don't have access to that currently, but well guess that's the case