Version 1.5.1.1
April 29, 2021
Fixed
- Fixed bug preventing saved payment sources from populating payments
Version 1.5.1
April 22, 2021
Fixed
- Fixed bug preventing saved payment sources from populating payments
- Fixed bug preventing saving of payment sources
Version 1.5.0
April 20, 2021
Added
- Added
UserFieldsEvent
for sending custom data with authorizations (documentation)
Changed
- The plugin now supports Commerce Omnipay 3.0
- The plugin now requires Omnipay: CardConnect 1.4.0
Fixed
- Fixed a bug where purchase transactions failed to validate correctly
- Fixed a bug where requests failed to send cardholder name if different from billing address
- Fixed a bug where requests using payment sources failed to populate cardholder name
Version 1.4.4
December 17, 2020
Fixed
- Fixed bug where expiry pattern wouldn't validate correctly in certain instances
Version 1.4.3
December 1, 2020
Fixed
- Fixed a bug where pasted card numbers might not update CVV validation
Version 1.4.2
October 30, 2020
Fixed
- Fixed a bug where successful zero-dollar card validations would return as failed
Version 1.4.1
October 22, 2020
Added
- Added
jmauzyk\commerce\cardconnect\variables\Variable
- Added
jmauzyk\commerce\cardconnect\services\AssetBundle
Changed
- Changed asset bundle source paths to be consistent with published url getter
Fixed
- Fixed payment form duplicate input ID
Version 1.4.0
October 21, 2020
It's now possible to tokenize using the CardSecure API via javascript. Tokenization method is selected in the gateway settings. For information on customizing form appearance and custom payment forms, see the documentation.
- Added support for saving payment sources
- Added ability to tokenize using CardSecure API via javascript
- Updated Omnipay: CardConnect to 1.3.0
- Added
jmauzyk\commerce\cardconnect\gateways\Gateway::getIframeNumberInput()
- Deprecated
jmauzyk\commerce\cardconnect\gateways\Gateway::getTokenizedNumberInput()
Version 1.3.1
August 20, 2020
- Updated tokenized number input to make UI in Craft CP
- Fixed order ID not displaying in CardPointe
Version 1.3.0
August 7, 2020
As of this release, payment forms generated using
getPaymentFormHtml()
will use tokenized card numbers by default via CardConnect's Hosted iFrame Tokenizer. For information on customizing form appearance, custom payment forms, and reverting to clear PANs, see the documentation.
- Updated
getPaymentFormHtml()
method to implement Hosted iFrame Tokenizer - Added
jmauzyk\commerce\cardconnect\gateways\Gateway::getTokenizedNumberInput()
- Updated Omnipay: CardConnect to 1.2.0
- Authorize and Purchase requests now correctly send the order id instead of transaction hashes
Version 1.2.0
March 12, 2020
- Added composer support for Craft Commerce 3
Version 1.1.0
February 12, 2020
- Updated to be compatible with new API URLs
Version 1.0.1
October 30, 2019
- Updated Omnipay: CardConnect to 1.0.1
- Fixed missing address
- Added address line 2 to request
Version 1.0.0
September 19, 2019
- Initial release