#stripe

jpo: you can update the subscription with a new plan, in case that's what you meant

Woet: is there anyway, where i can get a authorization for an amount and then with every sub capture, send it additional meta data ?

ozonelc: what kind of metadata? you can authorise a payment and then capture it within 7 days

Woet: the API seems to provide place holders for metadata only on the initial auth

well you can update the charge

where you can update the metadata

te use case is that I want authorize for the full amount, but this amount is charged as multiple orders and want to tag each charge with a different order id

well you can do that using metadata

so user types in CC info only once, but sees multiple charges on his statement

each charge for a different order id

you can do that

and all these add up to the initial auth

as long as it's the same or less, it'll work

Woet: awesome. thanks...

wait

i am not certain whether you can capture the same charge multiple times

what is your use case?

because you could just create multiple charges (all of them authorised)

and then capture the ones you want

I have a cart with 3 items that totals to 100$

product 1:( 75$) , product2:(25$) and product3:(50$)

okay

I want the customer to type in cc only once and get auth got 150$

and why do you want to charge them separately

i mean it's possible

just authorise them separately and capture them separately

then I bundle product1 and product 2 ( sub total : 100$) into order #1

and product 3 (subtotal: 50$) as order #2

and the send in two charges

okay

so authorise 100$ and 50$

and then capture them later

and each charge as the order # in the meta data

yes

would not the customer type in CCC info twice ?

I was hoping not to create the customer objects

no

you turn the token into 1 customer

and then create charges using that customer ID

you mean use https://stripe.com/docs/api#create_customer to get the customer token ?

and use that ?

yes

I was hoping to not create the customer object

why?

I ave to maintain the customer token in my DB and an additional API call

was trying to avoid that

you don't have to store the token in your DB

if you insist

but.. i don't really see the problem with that either

so, the next time the customer uses the same CC card, will I be assigned a new customer token ?

that I can use and throw ?

well

you either store the customer ID

and you will only ask for the CC info once

or you don't store the customer ID

and you ask for the CC info on each order

thats whats I wanted clarification on.

I dont seem to have a choice but work with the customer object

i still dont see the problem with that

im not sure how else you think it'd work

as I dont want the customer to type in the CC info twice for the same shopping cart checkout

it won't be needed for the same checkout provided you create all the charge objects straight away

(wont be needed to store the customer ID)

I was hoping that I could get an auth (150$) and charge them in chunks ( order #1: 100$ and order #2: 50$) with each chunk having the order id tag in the mete data

*meta

yes

you said that

that is possible.

with or without storing the customer ID

yes, this is my preferred option

okay

that is possible.

thanks.. just wanted a validation that this would work

create a auth charge for each chunk

capture them later

an auth charge *

but what I want to do is : 1 auth (150$) and 2 captures(100$ + metadata= order #1) and (50$ + metadata= order #2) without registering the customer object

yes

you mentioned that a few times

will try it out

i am pretty sure you cannot do 1 auth with 2 captures

create a customer object, then do 2 auths

ok..

no need to store the customer ID except temporarily

ok

Woet: thanks for your time

no problem

Woet: However, I am still disappointed with lack of response from stripe support

nothing i can do about that

I know, hoping that stripe support read this message :)