#benk6763

1 messages · Page 1 of 1 (latest)

narrow spruceBOT
unkempt willow
#

Hi there!

sleek stream
#

actually we are a platform who are integrating directly with GooglePay (we are to decrypt the encrypted payload) and thus not using Stripe as a Google Pay "Gateway". We are essentially becoming a Gooel Pay Gateway ourselves

unkempt willow
#

So you decrypt the Google Pay tokens on your end, and then want to pass the decrypted contents directly to Stripe?

sleek stream
#

yes as I mentioned we have the decrypted PAN (additionally the ECI and cryptogram) which we then need to pass onto Stripe through a server API

unkempt willow
#

Yes that's possible to do with the PaymentIntent API. However you need to contact Stripe support to get the instructions on how to do this.

sleek stream
#

just to clarify we will not use the Stripe Checkout or Element since we have our own hosted payment page. I mention this as usually this sort of conversation is being navigated towards those Stripe solutions which we are not using.

#

is there a specific Stripe Support person we need to speak with since I have already contacted Stripe Support and I was being sent a generic API link

unkempt willow
#

I understand, it's possible to supply the DPAN and cryptogram directly to the PaymentIntent API, so without using Checkout or Element.

sleek stream
#

unfortunately I find Stripe Support not very "tech friendly" and usually we go through at least 3-4 hops until we get out the relevant technical information we are seeking

unkempt willow
#

Let me double check something

sleek stream
#

thanks

narrow spruceBOT
cunning ether
#

👋 taking over for my colleague. Let me know if there's any follow-up Qs I can answer!

sleek stream
#

thanks tarzan. I understand there is a Stripe API to send the DPAN but wondering if this same API also support sending the 3-D Secure cryptogram bits (ECI, cryptogram)?

cunning ether
#

taking a look, sorry I didn't see that your question wasn't answered my bad

sleek stream
#

that's ok

#

I know that for the ApplePay token it's the PaymentMethodCreateParams.Token which is being utilised when the PaymentIntent object is built. But for the Google Pay integration it's the decrypted payload message (pan, expiry date year/month, ECI, cryptogram) which I'm not sure about since the PaymentMethodCreateParams.CardDetails builder doesn't expose any of the 3D-Secure related cryptogram detail fields

cunning ether
#

we can take it from there if you want