Commerce Ogone Alias

The Commerce Ogone Alias module adds support for aliases when using the Commerce Ogone module for payments. Aliases allow customers to store their payment information for reuse on their next purchase.
The merchant can use the aliases for recurring payments without formal confirmation by the customer. The payment details are stored on the Secured Ogone servers. In Drupal we only store the Alias. The alias cannot be used by other systems if it were compromised.

What do you need in your Ogone configuration?

1. You must request an account for Ogone (You can start with a test account here!)
2. DirectLink must be enabled
3. Alias Manager must be enabled. Their excellent support team will do this for you in test, but in production you must pay an additional subscription cost, before you can use it.
4. You must create an API user. Go to the User tab in your configuration, create a user and make sure you check 'Special user for API (no access to admin.)'

What will change when visitors pay with Ogone?

1. On the payment page, they will see a checkbox to give Ogone permission to store their payment details
2. When users make a second payment, their credit card information will be prefilled and just need to enter their CVC code.
3. When cron runs, orders will be sent to Ogone, if they are in the status you specified in the DirectLink configuration of the Alias module.

Dependencies

You'll understand you need to set-up Drupal Commerce with the Commerce Ogone module before you can use this module.

Alias manager works with VISA/Mastercard, but not with Bancontact/Mistercash payments. :-(