#Andrew-PaymentIntent
dusty lantern
hi there! it's not possible, you should specify the transfer_data[destination] when creating the PaymentIntent.
The possible parameters when capturing a payment intent are listed here : https://stripe.com/docs/api/payment_intents/capture#capture_payment_intent-transfer_data
low grail
Ah so if i'm using the Terminal iOS SDK what's the correct approach?
setting transferDataDestination seems like
dusty lantern
sounds about right, does it work?
low grail
Yep seems like it. Also application_fee_amount doesn't have to be set via terminal API and can be set when actually capturing it serverside. About to test it now stand by.
Oof gotta update my server to remove the destination parameter. Will follow up in a little but i'm pretty confident it'll work.
low grail
@dusty lantern Follow up question. (everything works) But i'm curious,
Why does the stripe documentation not have hash details for card_present on PaymentMethod but the API returns valid details?
Oh i see. PaymentMethod doesn't have hash information about the details but the Charge's payment_method_details has hash information about the card_present property/hash
That's weird/inconsistent
solemn phoenix
👋 stepping in and gimme a few mins
Curious what do you see inside your PaymentMethod's card_present?
low grail
It might be in the logs let me go check. I only noticed because the Stripe library i maintain didn't have an updated PaymentMethod type for card_present gonna have to do an update this weekend. But basically i created a PaymentMethod via TerminalSDK and after capturing a payment intent serverside, I expanded the payment_method while capturing it. But when i want to update the library to have the hash details the docs don't have them.
@solemn phoenix Also here's the request for the capture/expand flow. i didn't see a card_present hash in the payment intent payment_method hash. req_b9PlKEvEAyXurO
And in the same PaymentIntent response i have the details nested in the charges 🙃
solemn phoenix
what if you expnad payment_method.card_present?
low grail
Well currently I'm just expanding payment_method and have been for about a year or so and just being able to get the card details back on payment_method so i'd imagine specifying a specific payment_method.type wouldn't necessarily have any extra benefit (unless card is expanded by default for whatever reason.) But for now i'll just reach inside of the charges, i don't have a super simple easy way of retrying that request at the moment.
low grail
But the docs not having a hash body as well as the dotnet library for example is slightly worrisome
solemn phoenix
The purpose is to see if there is actually data inside the PaymentMethod object
Yes maybe we haven't documented it
low grail
Right one sec. let me setup a quick route locally
Can you actually expand payment_method on PaymentIntent via the retrieve API?
solemn phoenix
Yes, should be possible
