#berserker2605

1 messages · Page 1 of 1 (latest)

austere shoreBOT
covert mango
#

Hello đź‘‹
I'm not sure I fully grasping the question.

Do you have a screenshot of the UI you're referring to?

gleaming solstice
#

i don't have the screenshot from google but i can provide the transaction if from my stripe does that help ?

covert mango
#

sure

gleaming solstice
#

ok a moment

#

Authorisation details
ID
iauth_1OSGrfAiA3o4oEJms9dy4O6T

#

9mad = 0.72ÂŁ at the time of the transaction

#

essentially google will show a window that says we will take 0.XX amount they don't say how much is that and suppostly i need to later give them that XX so that they know i'm the cardholder it resemble paypal verification to link cards if you're familiar with that

covert mango
#

Gotcha. Yeah, I see this was rejected due to missing SCA. It is possible that the issuing rules you have requires 3DS before any charges can be made to the issuing card.

The flow you're describing is likely some sort of micro-debit flow where the amount they deduct shows up in your statement and then you provide the exact amount to verify.

I understand that support team was unhelpful the last time you talked to them but I'd have to recommend you go through them for this as they're better equipped to look into what caused this and escalate accordingly
https://support.stripe.com/?contact=true

gleaming solstice
#

is there a way to cancel 3DS for small amount transactions ?

#

i see here

#

Exemptions

#

how to add this

#

ow_value_transaction Transactions below 30 GBP or EUR are considered “low value” and might be exempt from SCA. If the exemption has been used five times since the cardholder’s last successful authentication or if the sum of previously exempted payments exceeds 100 GBP or EUR, then the exemption doesn’t apply, and the cardholder must be authenticated.

covert mango
#

I'm not sure as I'm not familiar with the sort of controls issuing cards have.. I believe support team should be able to help with this too.

Based on how I'm reading the docs, the authorization object should have specified following already. So in this flow, Google would need to send those values when trying to authorize

      "type": "low_value_transaction",
      "claimed_by": "issuer"
    },```

I could be reading the docs incorrectly, i'm not totally sure. Support team should be able to confirm all of this