#stripe

:\

Back yet tr12?

i am guessing not too many folks around today. i just had a question about the email receipt_id, and what way to test that out using the Stripe Test environment. The emails dont get sent in the test environment, but does a fake receipt id get attached to the response when the customer is charged?

andythornton: receipt ids only get set when the receipt is sent

Ponny: well, that took longer than expected

sorry about htat

Hi there. I'm trying to create a customer with a subscription, and getting an error that the "source" object of type "token" isn't supported

Am I missing something?

I'm getting the token from Stripe Checkout, and passing that as the `source` param to `stripe.customers.create`, but it's giving me the error that token isn't supported

seanadkinson: what's the verbatim error message?

type: "invalid_request_error"

message: "token is not supported."

param: "source"

tr12 ^^

it looks like you want to set source=token_id, not source=full_token_object

although that's an admittedly unhelpful error message

oh, interesting, let me try that real quick

tr12: Ha, thanks, that worked

yeah, before the error message used to say like "{{JSON representation of token object}} is not a valid token" or something along those lines

funny thing is that I had that code written first using just the id, and then checked the docs, and it said it should be an object

so I figured it needed to be the full token object

so, what's going on here is that technically you can supply a full representation of a card as the source (although this is a terrible idea re: pci compliance)

so its interpreting it as the card object, but it has type: token, which isn't supported

and when you try to pass the entire token, it thinks you're trying to do that

exactly

yep, i get it

i think if it said something like "string or object" here: https://stripe.com/docs/api/node#create_customer

that would've helped me out to just pass the id initially

since it said object, and i have an object with "type: token", i was thinking i was good

anyway, thanks a lot!

yeah, that's reasonable feedback

honestly, 99.99% of all merchants don't want to pass a full card object anyway because of PCI

so I'd lean towards de-emphasizing the card object entirely

cool, i'll be back if i get stuck again. really appreciate you guys and what you've made

Hi Stripe Savants - Quick question here - I'm working with connected (managed) accounts and attempting to set up an interface where they can issue refunds. When I list their payment history, I'm just getting txn_ (transaction) ids, not ch_ (charge) ids.

I assume this is because it's actually a transaction from my platform to their managed account

To refund them, do I need to trace this back to the charge ID on my platform's account? If so, is there an easy way to reference the charge ID from the transaction id?

hi everyone, I am integrating stripe in nodejs app, while using the 'create customer' api method. I am passing the token generated from stripe.js as 'source'. But getting this error "error creating stripe billing: { [Error: token is not supported.]". replacing it with car info dictionary works just fine. Any idea what's the problem?

"card* info dictionary"

Rana_: it sounds like you're passing the entire token object as the source, when you only need to pass the token id

Hi Stripe Savants - Quick question here - I'm working with connected (managed) accounts and attempting to set up an interface where they can issue refunds. When I list their payment history, I'm just getting txn_ (transaction) ids, not ch_ (charge) ids.

I assume this is because it's actually a transaction from my platform to their managed account

To refund them, do I need to trace this back to the charge ID on my platform's account? If so, is there an easy way to reference the charge ID from the transaction id?

you'd want to refund the original charge on the platform side, yes

@tr12, ah, ok. cool, thanks. I am gonna try that.

V27: iirc, there isn't an easy way to go from a py_*** id to a ch_*** id on the platform side

I think you'd need to maintain a local db that stores that mapping

Is there a better way to list out the charges that the connected account received that would give me that info?

the balance transaction on the platform has the payment id, so you can go from a charge id to a payment id, but the other direction is more complex

I assume querying charges won't work because the charge is on the platform, not on the connected account, but correct me if I'm wrong

is anyone here?

V27: that's right

my_name_is_steve: yes

V27: you presumably already have a row in your local db for each charge made, so that it's connected to whatever it needs to be connected to in your business logic.

hello! i am trying to pull the customer ID from a stripe customer object but everything appears protected

my suggestion would be to add a column for the connected account / seller that the charge is associated with, so you can filter by that account

can anyone help me out with that?

this is in php

my_name_is_steve: so $customer->id doesn't work?

Got it - so just to confirm, the best way to get the list of payments that platform has received would be to use the transaction history, searching for type 'payments', no alternative way to list those payments out, correct?