#lucas-barbosa_terminal-surcharging-beta

1 messages · Page 1 of 1 (latest)

pale agateBOT
#

👋 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/1277741753243402263

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

pearl sky
burnt nimbus
#

Yes, however this request is sent by the simulated reader. I'm not setting the amount_surcharge value in the request

#

It seems the simulated reader is sending the empty request to confirm the payment. However I've not found a way to set the amount_surcharge in the simulated reader

pearl sky
#

How are you configuring surcharging with the physical reader?

burnt nimbus
pearl sky
#

Sorry these are dashboard links and, because of that, I cannot use them. Can you share just the Request IDs? req_XXXX

burnt nimbus
#

Sorry. Physical reader: req_ZQyViBH8l0RdaE
Simulated reader: req_Fus7CZ11LrlJa3

pearl sky
#

Thanks!

#

Okay so you are sending the same confirm_config to both the Physical and Simulated readers.

burnt nimbus
#

Correct, however in the next event (POST /v1/payment_intents/pi_xxxx/confirm), the simulated reader is not sending the amount_surcharge

pearl sky
#

Oh, wait this is a preview feature that isn't fully GA'd yet

#

Unfortunately we are not able to help with Beta functionality here.

burnt nimbus
#

Oh, ok. Thanks anyway

pearl sky
#

There should be a contact that enrolled your account in the Beta. You should be able to reach out for clarification whether or not the simulated reader supports surcharging through them.