#mastjoe_webhooks

1 messages ยท Page 1 of 1 (latest)

sweet pastureBOT
#

๐Ÿ‘‹ 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/1447704337580036253

๐Ÿ“ Have more to share? Add more details, code, screenshots, videos, etc. below.

full warren
half python
#

Thanks for your response @full warren , but from samples I have, the both have contactless_emv value

full warren
#

Oh yeah you can't separate contactless chip card and mobile wallet

#

They're grouped in that same category

sweet pastureBOT
half python
#

The samples I have none has wallet object under the card_present object. Neither the NFC nor terminal charge

full warren
#

Can you share an example payment method where a wallet was used but the wallet param is empty?

obtuse basin
#

๐Ÿ‘‹ codename_duchess has to head out, i'll be taking over the thread. Just getting caught up.

half python
#

Alright

#

welcome @obtuse basin ,
I am trying to distinguish between an NFC charge and that of terminal from the Stripe charge object, as both appears as card_present and read_method is equally contactless_emv

obtuse basin
#

Do you have the request ids from those mentioned examples we can take a look at?

half python
#

Yeah I do.. will share in a bit...

#

Terminal charge event => evt_3S12p2GOKMeqlOVU0Evplc9N (req_QHlyGnaljHnESJ)
NFC charge event => evt_3S12oUGOKMeqlOVU001U1Gw3 (req_pdeuBXntQNZxZW)

wise flower
half python
#

The metadata field.
Due to the inconsistency of the metadata field, I sought a more standardized and reliable way to distinguish them.

#

some metadata field are created in the course of creating the charge which helps to tell which is terminal or nfc, but sometimes does not happen, so need something original from Stripe to make that distinction

wise flower
#

What does this nfc_ios mean?

half python
#

honestly I don't know how that determination is done as it is handled by a separate team, I would've depended on it but it is not consistent

#

the suffix comes as either ios or android I think that the suffix represents the OS of the contactless device maybe

wise flower
#

Based on https://dashboard.stripe.com/acct_1EwQweGOKMeqlOVU/logs/req_pdeuBXntQNZxZW where the card information is sent to Stripe through, there wasn't any indication that this is a NFC payment. Do you have any charge object that you can successfully determine this is a NFC payment when you cross check with Stripe charge data?

half python
#

I honestly do not know, I was trusting that the metadata value was correct. How correctly can I tell that a charge is NFC ?

wise flower
#

From our data, I can't tell whether this is a NFC transaction. If this is a NFC made from a wallet payment method, card_present.wallet should have the wallet payment method type. However, this field is not present for ch_3S12oUGOKMeqlOVU0Ucrduwi. It will be helpful for us to understand how your system determines nfc_ios. Does someone at your side enter this value manually through POS, or is there any automatic way determined by your system?

half python
#

I think it automatically updated. I will probably enquire from the team in charge to know how that is determined .
Just to be sure, do you mean that every genuine NFC transaction is expected to have a wallet payment method, card_present.wallet ?

wise flower
#

Yes! Take ch_3ScDaEGOKMeqlOVU1zxND2lj as an example, its charge.succeeded event showed the card_present.wallet as apple_pay: evt_3ScDaEGOKMeqlOVU1rd4twah

half python
#

Alright. Thanks for the clarifications.

wise flower
#

No problem! Happy to help ๐Ÿ˜„