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

Ogone authorize does not work with alias #3109

Open
ZenCocoon opened this issue Jan 14, 2019 · 0 comments
Open

Ogone authorize does not work with alias #3109

ZenCocoon opened this issue Jan 14, 2019 · 0 comments

Comments

@ZenCocoon
Copy link
Contributor

ZenCocoon commented Jan 14, 2019

Currently, the authorize method is looking if the payment source is a brand, however, this payment source might be an alias string and therefore not respond to the brand method.

Actual code at https://github.com/activemerchant/active_merchant/blob/master/lib/active_merchant/billing/gateways/ogone.rb#L152
action = (payment_source.brand == "mastercard") ? "PAU" : "RES"

This was done to allow the use of a pre-authorization instead of authorization (which gives an extra 23 days hold) for Mastercard, however, as documented on Ogone https://payment-services.ingenico.com/int/en/ogone/support/guides/integration%20guides/e-commerce/other-optional-fields

PAU/pre-authorization can currently only be used on MasterCard and Visa transactions and is supported by selected acquirers. This operation code cannot be set as the default in your Ingenico ePayments account.
Should you use PAU on transactions via acquirers or with card brands that don't support pre-authorization, these transactions will not be blocked but processed as normal (RES) authorizations.

Therefore using PAU all the time should be safe, as the gateway will automatically fallback if not supported for the given card.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant