#stripe

dqsf: {

error:

message: "'usd' is currently the only supported value for the currency parameter. If you will only be charging the card (not transferring to it), you should omit this parameter."

type: "card_error"

param: "currency"

code: "invalid_currency"

}

Ew, that didn't post very nicely did it.

dqsf: it did not recoginse "refund_application_fee = true"

timuruski: Can you share an event in your logs where you're seeing this so I can look it up?

dqsf: what was wrong with my codes pls?

iar_xxx

stripe316: Looking

dqsf: many thanks

dqsf: iar_6LcUc9JIsnBKo3

stripe316: instead of retrieving the refund and trying to update can you pass all these properties at the time of creation

Timuruski this is because you're passing currency to Stripe.js

Timuruski stripe.js doesn't expect a currency to be passed to it

stripe316: pass $ch->refunds->create(array("refund_application_fee" => true,"reason"=>"requested_by_customer"));

dqsf: do you need to retrieve it first?

stripe316: no. if you look at the api docs the only value you can update a refund with is metadata

timuruski: markin is correct here, don't pass amount and currency when creating a token. You'll want to specify these in your backend

To my knowledge we've always done this, but I'm confirming that.

The last time our payment JS was updated was June 2014. Looking into dependency changes that may be related.

timuruski: Are you hosting stripe.js locally, or pulling from stripe

Checking that.

I didn't write the original implementation, need to dig around.

It looks like we are hosting stripe.js, which is compiled into our main JS file. Looking to see if there are recent changes to our JS dependencies.

Timuruski on a related note only the newer stripe.js versions are pci compliant.

I would recommend including it from https://js.stripe.com/v2/. Self hosting it can lead to these kinds of quirks and breakages.

The currency issue is related to the tokens api that stripe.js calls, the currency parameter is undocumented and it looks like there was a breaking change with it since it was undocumented

I'd like to get us to that version, first need to fix this issue. I'll try ducking the explicit currency call and see if I can replicate.

Hi, setting up stripe connect with managed accounts

dqsf: any idea why i got error message "error_msg": "Invalid refund reason not good product" - here is my code

dqsf:$refund = $ch->refunds->create(array("refund_application_fee" => true,"reason"=> $reason_cancel));

stripe316: there are only several reasons you can use here

duplicate, fraudulent, and requested_by_customer

stripe316: a list of valid reasons is listed here https://stripe.com/docs/api#create_refund

I'm using an example from a US rails app that uses account_number and routing_number. As I am setting up in the UK can I just change routing_number to sort_code, willl stripes API recognise this

If you want to add a description, store it in metadata

dqsf: Removing the explicit currency eliminates the error message. I need to confirm that our transactions are actually still in CAD though. I'll let you know what I find.

what generally triggers a govt. ID being required on a managed account?

marshal: You can definitely try that, at the moment Stripe doesn't have a uk-specific test bank account number though

timuruski: what determines the currency of the charge is your server-side code

MDrollette: my guess is some of the automated checks raised some flags

@dqsf ok but should we just call it routing_number and use the 6 digit short number when we test with real money or can we call it routing_number? Happy to test with american 9 digit number for now.

<@dqsf> ok but should we just call it routing_number and use the 6 digit short number when we test with real money or can we call it routing_number? Happy to test with american 9 digit number for now.

dqsf: ok but should we just call it routing_number and use the 6 digit short number when we test with real money or can we call it routing_number? Happy to test with american 9 digit number for now.

marshal: yeah, just call it routing_number but use the sort code

marshal: for iban account numbers you don't need to pass routing_number

marshal: yes, that's correct

dqsf: Response body for the subscription says currency is CAD. The server-side code gets the currency from the invoice. Since the only bank account we have is in CAD, am I safe to assume that is where the invoice gets its currency from?

timuruski: you set the currency when you create the subscription plan

is there a way to bulk-export Card fingerprints from our Stripe acct? would like to store the fingerprint in our database so that we can limit promotions to once-per-card

timuruski: So that's where the subscription is getting the currency from. https://stripe.com/docs/api#create_plan

dqsf: many thanks. It works now

Is there a sales number I can call to ask about setting up an account

This is before my time, but I think older versions of stripe.js may have done an authorization for an amount and currency, that's why those params are there in some older version

/msg markin: Thanks

ifnull: Reach out to sales@stripe.com, they can set something up with you

ifnull: You can also get started by registering an account here, https://dashboard.stripe.com/register

dqsf: Looks good to me, I think this is mostly sorted now, I'll patch and deploy, then open a ticket so we can upgrade away from self-hosted stripe.js. Thanks for the help!

thanks

chatra: Not directly, you'd want to retrieve a list of all of your customers, iterate through them, copy the fingerprints of the attached cards https://stripe.com/docs/api#list_customers

dqsf: ah okay, thanks. so the customer CSV export does not include card fingerprints?

Hello!

hi lajarre

I'd like to know if I have any chance of breaking something when upgrading my API version from 2013-12-03 to the current one, knowing that I use only charges (stripe.Charge.create() in python)

lajarre: there is a chance, what I would do is set up a new instance of your program in test mode and set it to use the latest version of the API using https://stripe.com/docs/api#versioning

any idea? I'm a bit afraid because it seems I can't choose to upgrade the test API before the production one...

lajarre: and run some tests

markin: ok

makes sense

Thanks!

lajarre: You can see the differences here, https://stripe.com/docs/upgrades?since=2013-12-03

Hi. I have a question about how to best implement something in stripe. We are converting from Blanced.

right now we provide a platform where in some cases we will pay for part of a transaction as part of someone signing up for our server. We do this now by basicly debiting our account and the credit card of the customer.

We then credit another account with the two charges.

You know let me restart my question.

We are a platform where people can create an event and charge people to attend the event.

ciddennis: basically you want to subsidize your customers purchases from a vendor?

One feature we have is if you get one of your friends to join our platform and pay for an event then we will give you a $10 credit.

Yes, exactly

So the idea is that once we get payment from the person going to the event we will subsidize the charge with our own money and pay out the full amount to the event organizer.

so coming from balanced you should have access to the ACH-In beta, so you could charge yourself and then send that money to a connected account

it would be 2 seperate payments to the connected account, but you could combine them into 1 bank deposit once it reaches their stripe account

I did not see that feature yet. Do yo happen to have a link to the api docs?

or if you just keep a balance in your stripe account, you could use the special case transfers feature https://stripe.com/docs/connect/special-case-tr...

ciddennis: which feature don't you see, the charging yourself?

I did not see the docs on the ACH-beta

Hello, using connect to create plans and subscriptions on our app users behalf. Getting a "Uncaught exception 'Stripe\Error\InvalidRequest' with message 'There is no token with ID tok_..." error when I attempt to create the customer and subscribe to the plan with the token. Works for single charges, maybe I need to be using the clients pub/private and our keys differently. Any ideas?

Token is from client's public key.

Stripe\Stripe::setApiKey is using our private key

That setup works when creating single charges.

Hi there, i'm working with Customer when i'm creating a charge. But if a customer wants to pay with another card than the one he used when i created this customer, how can I do ? Thanks

i8flan: When you are attempting to create the customer and subscription on the connected account are you passing the Stripe-Account header?

Is there anyone here that can help me with transfer problem I am having in stripe

irctc824: You can pass both the customer id, and a card id of a particular card on that customer when creating a charge

dqsf: I don't think I am. I'll have to look that up and see what it is.

dqsf: i put the token (i'm working with checkout) in the source parameter ?

i8flan: So if you're using the client's publishable key to generate a token, and you want the customer and subscription to live on their account you'll need to use that to make sure that the action happens on their account, rather than your Platform account

Erica_: What's the issue you're having? We're mostly here for tech help, if it's specific to your account you'll want to email support@stripe.com

dqsf: thanks, makes some sense. I'll dig into it a bit. Thanks for the lead!

irctc824: If the customer wants to pay with a new card you can present them with the card field again, and then add that token to the existing customer.