This project is not covered by Drupal’s security advisory policy.
Opayo (formerly Sage Pay) payment gateway for Drupal Commerce 2.x. It uses the Opayo Pi API with 3D secure authentication happening inside an iframe.
Features
- 3D Secure authentication step is done inside an iframe during the checkout process, allowing consistent presentation to the customer.
- Supports Payment and Refund transaction types
- Add Opayo Transaction entity lists to the admin pages
- Supports collecting customer phone number during checkout - a requirement for 3D Secure Authentication
- Periodically delete expired payment methods and Opayo transactions
- Cardholder PAN details are only submitted to Opayo and never to the Commerce back-end, limiting PCI compliance to SAQ-A/SAQ-A-EP
- Can work (subject to some custom development) with 'Commerce Webform Order' and take payments from a webform rather than a cart.
Post-Installation
see README
Additional Requirements
Dependent modules (other than commerce): phone_international and queue_unique
Similar projects
Commerce SagePay integration uses the Opayo Pi API. The main differences is that it doesn't (at time of writing) support collecting the required customer telephone number, it collects the customer credit card details server-side for tokenisation (rather than from the customer's browser) and 3D Secure Authentication doesn't happen inside an iframe. However, it supports Repeat transactions.
Project information
- Project categories: E-commerce, Integrations
20 sites report using this module- Created by mwjansen on , updated
This project is not covered by the security advisory policy.
Use at your own risk! It may have publicly disclosed vulnerabilities.
