#.xaositect
bright plume
Hi, it looks like you're using our legacy Charges API. I recommend that you migrate when you can.
opaque rampart
I'd love to, just as soon as someone gives me a budget for it! Anything I can do in the meanwhile?
This is what we were given as an example ( a couple of layers of middle management in between ).
The oddity is that we don't ship product
bright plume
~~Yeah, the Charges API does not have billing data that I why I recommended Payment Intents as it does, https://stripe.com/docs/api/payment_intents/create#create_payment_intent-payment_method_data-billing_details.~~
Looking further
opaque rampart
thank you!
bright plume
Sorry, I misspoke. The billing details are on the Token or Source of the payment method used. So as long as the Token has the billing details it would be supported on Charges API.
opaque rampart
We are collecting postal codes on card creation ( using stripe elements fields ). So it is peculiar that stripe wouldn't have that data.
bright plume
Can you share an example request so I can further look at this?
opaque rampart
an example charge request?
{
"description": "Retainer",
"statement_descriptor_suffix": "BEAUTIFUL MEM...",
"metadata": {
"environment": "PRODUCTION",
"installmentID": "clsi3t1800019id08tog89eny"
},
"statement_descriptor": "RPC* BEAUTIFUL MEM...",
"currency": "USD",
"customer": "cus_PWNyyACuQJL0i2",
"capture": "true",
"transfer_data": {
"destination": "acct_1OA1Z3FRYieADkFH",
"amount": "48750"
},
"source": "ba_1OjA15FXc3zoUgUu8zlPv79l",
"amount": "50000"
}
yes
Sorry, request id. Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request
opaque rampart
here's the req id for the above req_L6w2MA96nkixzH
Its prod... let me know if you'd prefer a test charge, apologies
bright plume
I'm just looking for an example where there was no zip code data
opaque rampart
That's not clear to me... is there a way to filter charges via dashboard or API request that do not have a postal / zip code associated?
bright plume
Hm, let me see if I can identify it from your account. I assumed you had a few examples already
opaque rampart
No examples were passed down to me, alas.
I've asked whether an example was given, however
idle moonBOT
bright plume
I found some examples. Looking at this request, https://dashboard.stripe.com/logs/req_p23EWRG4dEOU78 for instance, I do not see billing details passed.
opaque rampart
It is interesting because my "logged in" docs https://stripe.com/docs/api/charges/create
do not suggest a billing details param, though the return fields do.
bright plume
The reason being, the billing details are on the Token object: https://stripe.com/docs/api/tokens/create_card#create_card_token-card.
bright plume
Yes, you need to capture the billing details when you create the Token.
opaque rampart
And I believe we could update the source with those details after capture?
after capture of payment method, before payment
knotty narwhal
👋 taking over here. Happy to help
opaque rampart
Thanks @bright plume have a good night
Hi @knotty narwhal
Would you like a summary, or to read through the above?
knotty narwhal
I read through it, no worries 🙂 Ty
Yes I believe you would want to pass the billing details when you create the Token. Let's don't use the word "capture" since that's a different term in Stripe API
to avoid confusion
opaque rampart
I'm just going to guess however, that I need to be using the payment method API https://stripe.com/docs/api/payment_methods/update because it seems like the source API https://stripe.com/docs/api/sources/update does not have those properties.
knotty narwhal
No, that's a different API and a backend API. We are looking at Create Token API from frontend (stripe.js). Here https://stripe.com/docs/js/tokens/create_token?type=cardElement#stripe_create_token-data
opaque rampart
sure, but then we turn that token into a source on the customer. The question is, can we do that with the update source API
we could easily add that to our front end creation methods, but...
most of our payment methods are persistently attached to customers, currently via the createSource and updateSource APIs.
knotty narwhal
Yes I think Update Source API has an owner field that you can pass address in, but not sure if that will be effective as the billing details on Create Token (says Radar)
You might want to test it out
opaque rampart
I just want to make sure we have a way to remedy existing customer payment methods
Because if we don't, that is a huge problem.
knotty narwhal
Ah makes sense. To clarify where would you want to use the collected address? Is it Radar or something else?
opaque rampart
AFAIK we're not currently using radar. But somehow we are being given elevated transaction costs, as I understand it, because zip codes are missing from payments... Hence why I am here.
I'm just a humble code monkey.
opaque rampart
👍
knotty narwhal
Alight I found some context, but can you provide me an example Charge Id ch_xxx? or an example Source on existing customers that you want to remedy?
opaque rampart
yes one moment
card_1NwzGZFXc3zoUgUuHBvzR9l1
my very own card
knotty narwhal
Yeah but can I have a Charge Id?
One created by your flow with Token and Charge API
opaque rampart
this was ancient ch_1GNNETFXc3zoUgUueb4ibJkD
knotty narwhal
Uhm that was a different card.
To be clear here is the request to create card_1NwzGZFXc3zoUgUuHBvzR9l1 https://dashboard.stripe.com/logs/req_0nVy4cRdyNpNDr
opaque rampart
Sorry, I didn't realize you wanted the payment method to be connected to the charge
knotty narwhal
I see it generated tok_1NwzGZFXc3zoUgUuAJmwntTi on 2023 Oct. Do you have any Charge Id using this token?
opaque rampart
We don't make charges with tokens. We turn the tokens into sources, and then make charges with the created sources.
opaque rampart
Looks pretty banal. Yes, I see that it doesn't have a billing details property, is that what you're saying is missing?
Hence my comment earlier about that not being available on the documentation for the charge API.
the source has an address_zip property, fwiw
knotty narwhal
Yes that's where I am trying to look closer it. This example (this Token and this Charge) definitely has zip
so it's not downgraded fee
opaque rampart
ah, how can you tell? Is there a way I can look at a charge and see that?
knotty narwhal
Yeah on https://dashboard.stripe.com/logs/req_ekKZh4X9eblHyq you can look at the response. It has
address_zip: "97215",
address_zip_check: "pass",
this charge for example, the opposite req_p23EWRG4dEOU78
opaque rampart
okay...
So the business seems like it is pretty much
collecting postal codes and address line 1s for sources that don't have them
getting that data from users on the token creation
Would that seem like a reasonable guess?
Short of updating our integrations, that is...
knotty narwhal
Yeah let me puts it together. So your current flow is
- Create a Token in frontend. This API generated a Token (tok_xxx) and also a Card (card_xxx)
- Use the Card directly in the
sourceparameter to create a Charge.
Now you have a lots of pre-generated Tokens and Cards, which is lacking zip codes. You are looking to a way to attach zip codes to them so all future Charge will have the zip
opaque rampart
yep
we don't hold onto the tokens... happily
Thank you so much for your time this evening
knotty narwhal
But you currently don't have any Source object (src_xxx), so I don't think you can call Update Source API anyway. That API needs a Source Id
opaque rampart
hmmm everything in our db is either a card_ or ba_
I assume our problem is card transactions, though I should confirm that.
knotty narwhal
Yeah that is Card (card_xxx). Hold on let me look at some API details
opaque rampart
seems like an easy thing to look for
"address_line1_check": null,
"address_zip_check": null,
knotty narwhal
Yeah looking right at it
Yeah I think that would be simpler. Just call Update Card and pass in the zip. Can you try it in Test Mode?
Your goal is, after updating, create a Charge on the updated Card and see if it has address_zip_check: "pass"
opaque rampart
Cool. We have a path. Thank you again
knotty narwhal
Np and good luck! Glad that helped
opaque rampart
Sorry for being so vague in my understanding of the requirements