battbot

[formal gulch]

pi_3NGrmfJ93KfFVesb1jizKx2B is one such payment intent

[wise swan]

The payment failed one second after the payment was created.

Your integration should be able to communicate that to the user

The API responded with this information

[formal gulch]

we communicate to the user that their payment failed due to invalid zip

but they still see the pending charge on their statement

end users think it means they got charged

this happens usually when a Google Pay token is sent to us and we attempt to charge using it

I don't know why a Pending charge is created in the first place

it would be nice if that Pending charge wasn't created at all.

usually if we were doing it with a Payment Method or a Card, it doesn't seem to generate this Pending charge on failure. Seems to only happen for Google Pay tokens

[wise swan]

Oh that is up to the issuing bank

The authorization for the charge was successful but the zipcode verification fails. It's up to the bank to remove the "Pending" charge from the account. This isn't something we can configure/control

[formal gulch]

when does authorization occur on the charge?

we didn't request an authorization. Was it part of the Google Pay token creation?

[wise swan]

It's part of making the charge

[formal gulch]

this doesn't seem to happen when payment fails for other reasons

[wise swan]

Postal code verification only occurs after we send payment details to the issuing partner (bank, BNPL, etc.). They first authozie the payment and then attempt to process it

[formal gulch]

I see

[wise swan]

Some failures occur before we send the information to the bank

so the bank doesn't see the charge

[formal gulch]

ok thanks