#NinjaMasta-terminal

1 messages · Page 1 of 1 (latest)

last storm
#

You will need the created Charge Id to confirm

#

Do you have the created Charge Id?

#

ch_xxx if it was Charge or pi_xxx if it was Payment Intent

errant kindle
#

pi_3LB7lsJttsoT29oo0FaHuxYp

#

The payment shows up in Stripe, but not when I query via the stripe.charges search api with the last4 digits (9969)

last storm
#

I think it's just the query. I do see a card_present ending with 9969

errant kindle
#

So is the query broken or does it just not work with the blank cards? I can make manual card entries with a fake 4242424242424242 card number and search by the last 4 digits (4242) and everything works, but when I try to use this physical reader with a blank card, the query doesn't ever return anything.

last storm
#

It could be Terminal's PI (card_present) is not compatible with Search API. Let me find out

#

How about payment_method_details.card_present.last4:9969 ?

errant kindle
#

Let me try

#

Yeah that seems to be retruning data

#

So is this just an issue with the blank card then or will I see the same behavior in production? I am using the api to perform order lookups to issue refunds. Which API call would be best to use?

last storm
#

Which issue? I believe card_present is suitable in case of a reader, vs card in case of online payment