#dlavoie-plannit_error
south fractalBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1370021538857877525
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
native jewel
in short, we are at our first production test with card present integration with ios sdk, the connected account that try it is able to connect to the reader, but unable to collect payment
don't have any details yet... want to see at first if terminal capabilities is activated for that account but can't see it
acct_1QQgGDE8aRHsBp2q
tml_FtowY3tEoVgeYL
tmr_FxoFwdZfiJqk39
velvet field
howdy, are you encountering errors for some accounts? My recollection is that if you have card_payments capability that also includes ability to process terminal, for otherwise supported regions/configurations
native jewel
you see that the reader was last connected earlier today, can you see a reason that payment could not be proceeded with that setup?
please note that location is registered a plateform level, is that a problem? it was not a problem at development phase since all works good in our test phase
velvet field
Let's take a step back -- that reader & location belong to your paltform account, not the connected account
What exactly are/were you trying to do?
Do you have an erroring request you can share to help me understand?
native jewel
we work on an integration with your mobile terminal sdk to enable our customer (standard connected account) to receive card present terminal payment.
we're at our first production test with real life context
our beta tester have his BBPOS WisePad 3 that he is able to connect to using bluetooth (Terminal.shared.connectReader)
velvet field
And this was working in your test environment with test connected accounts, but doing something different in live mode?
native jewel
correct
velvet field
With standard accounts the recommended charge flow is direct charges, which means everything happens on the connected account (locations, readers, payments intents etc).
This is why i ask about the location/reader on your platform account, this is inconsistent with direct charges on connected standard accounts
native jewel
we use destination charge
velvet field
Do you have an example of those successful test payments? eg pi_123
velvet field
Thanks - taking a look
While I'm doing that, can you say more about what is not working when you try this in live mode?
native jewel
I see that they try to do a 0.01$ payment, is that could be the problem?
I think I can do more investigation on my side... just want to make sure you see nothing wrong in the way we proceed and that this connected account has terminal capabilities, since when I fetch it via api I don't see terminal in their capabilities
"capabilities": {
"acss_debit_payments": "active",
"affirm_payments": "inactive",
"afterpay_clearpay_payments": "active",
"bancontact_payments": "active",
"card_payments": "active",
"cartes_bancaires_payments": "pending",
"eps_payments": "active",
"ideal_payments": "active",
"klarna_payments": "active",
"link_payments": "active",
"p24_payments": "active",
"transfers": "active"
},
velvet field
I see that they try to do a 0.01$ payment, is that could be the problem?
That could very much be an issue, there is minimum charge amounts
native jewel
I see
I will have a further look at this on our side
last question, is it normal that I don't see anything about terminal fetching that account by api?
velvet field
https://docs.stripe.com/currencies#minimum-and-maximum-charge-amounts
See here for minimum amounts per currency ($0.50 USD)
velvet field
last question, is it normal that I don't see anything about terminal fetching th...
Can you rephrase this? Or explain what you're looking at? I don't think I understand what you mean
native jewel
in other word, is there a way for me as the plateform account to see if my standard connected accounts have terminal payments enabled?
I expected to see something lile terminal in their capabilities fetching it via api
velvet field
No, and I don't think is relevant anyways given that youre doing destination payments from your platform
The relevant capability would be transfers in order to receive those destination charge transfers
But this should be clear from API errors, if youre encountering that
velvet field
I think your main issue is the amount being too small here
you also have an application fee set larger than the amount which i expect will fail
so you'll need to set an amount at least 0.50 CAD and an application fee not larger than the payment amount
native jewel
yes I see
velvet field
Actually the application fee doesnt seem to matter in my test, but would lead to a net negative for the connected account
native jewel
make senses
we will ask him to do another test with a larger amount
thank you for your help
velvet field
no problem, good luck with your work! 🫡 🇨🇦