#121940kz - Terminal
1 messages ยท Page 1 of 1 (latest)
Hi ๐
Have you tried creating a Payment Intent with the application_fee_amount parameter and use Terminal to collect payment?
Yes, i was creating the payment intent in this way
(can i paste code in here? just the intent piece)
Hi ๐ jumping in as my teammate needed to step away, yes you can share that here.
amount: amount,
currency: 'usd',
payment_method_types: ['card_present'],
capture_method: 'manual',
description: description,
application_fee_amount: applicationFeeAmount,
on_behalf_of: customerStripeAccount,
transfer_data: {
destination: customerStripeAccount,
},
});```
I'm not immediately noticing any concerns with that, and it seems to align with the guidance provided here:
https://stripe.com/docs/terminal/features/connect#destination-payment-intents
Are you running into problems/errors when you try to use that?
Actually i remember the problem i think. In my application, the registered terminal readers belong to my platform account. The payment method is cloned to their account. I think the issue had something to do with this
So i think the issue was that, if i am a customer who has signed up for my account, and i am processing a credit card for $50, the card_present terminal charge i needed to make sure when to the connected account... and not my platform account.
So maybe the issue was that the payment intent was being created on my account...i dont remember but I can test it tonight or tomorrow probably.
Can you see any issues with that? The customers terminal readers are all registered to my platform account. And the end goal is to process a credit card charge where the money goes into the connect account and an application fee remains in the top level parent account (the platform account)
So it sounds like in the past, you were using the Terminal flow to set up a payment method on your platform, but then cloning that payment method down to your connected accounts for use in direct charges.
Are you still intending to be able to share the payment method across connected accounts?
For this particular piece of my application, I dont have a need to share it across connected accounts. This particular feature i just need to do a charge and it's pretty much done at that point. I do have other features in my app yes, where I do need to have that cloning capability, and that is why all the readers are registered and belong to the platform account
I think the approach you showed above will work for collecting the application fee then. That will create the Payment Intent on your platform account, transfer the funds to your connected account, and allow you to retain a portion of those funds.
so basically, the payment intent will belong to the platform account, and technically the platform account will receive the money? Then i would need to do a transfer?
Yes, to the first bits, the actual payment will happen on the Platform. But you do not need to create a transfer, that will happen automatically based on the provided transfer_data and application_fee_amount parameters.
oh ok. And would a refund be able to be initiated by the connected account if needed, without any issues? I will test all of this again and report back if i have any troubles
I don't think the connected account would be able to request the refund directly, since the object that they'd be referring to is on the platform account and would therefore be outside of their visibility.
I had another quick question about terminal. Can the BBPOS Wise E somehow have like a keypad on it and it can be a mobile terminal where you can literally just type in an amount and charge a card? as long as it's on wifi
I have seen a lot of the Clover terminals can do that, there is a baseball park that has lots of beer vendors and they have terminals that look similar to the Wise POS E, where they can just type an amount and do a charge right there. I didn't know if that was something that can happen or is coming down the road?? It would be nice and fast if so.