Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

paymentMethodsTypeEnum.AndroidPay should be renamed to GooglePay #267

Closed
DrewNull opened this issue Jun 19, 2019 · 4 comments

Comments

Projects
None yet
3 participants
@DrewNull
Copy link

commented Jun 19, 2019

We are seeing a production and sandbox issue, since the evening of Monday 6/17, in which calls to getMerchantDetailsRequest are failing to deserialize the XML response due to a mismatch in paymentMethodsTypeEnum enum.

The SDK currently has AndroidPay as a value in the enum, but the getMerchantDetailsRequest now returns a value of GooglePay instead.

So, the following AndroidPay should be replaced with GooglePay:

Here is a developer forum thread with the same issue:
https://community.developer.authorize.net/t5/Integration-and-Testing/Request-Get-Merchant-Details-is-not-working-in-Sandbox/m-p/68033/highlight/true#M41316

Thanks

@DrewNull DrewNull changed the title getMerchantDetailsRequest returns GooglePay instead of AndroidPay paymentMethodsTypeEnum.AndroidPay should be renamed to paymentMethodsTypeEnum.GooglePay Jun 19, 2019

@DrewNull DrewNull changed the title paymentMethodsTypeEnum.AndroidPay should be renamed to paymentMethodsTypeEnum.GooglePay paymentMethodsTypeEnum.AndroidPay should be renamed to GooglePay Jun 19, 2019

@linman0x90

This comment has been minimized.

Copy link

commented Jun 19, 2019

We experiencing the same issue in a mission critical application.

@gnongsie

This comment has been minimized.

Copy link
Contributor

commented Jun 20, 2019

Hi,
We are aware of issues to this API. We are currently working to resolve this. A fix has already been identified and will be available on Friday.

Apologies for the inconvenience.

@gnongsie

This comment has been minimized.

Copy link
Contributor

commented Jun 21, 2019

Hi,
Our tests for this issue have passed. Travis CI builds have also turned green.
Can you validate if you are still seeing this issue?

@DrewNull

This comment has been minimized.

Copy link
Author

commented Jun 21, 2019

Nope--This appears to be cleared up now. Thanks

@DrewNull DrewNull closed this Jun 21, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.