Update Bank Account Payment

.editorconfig

@@ -0,0 +1,14 @@
+# CiviCRM editor configuration normalization
+# @see http://editorconfig.org/
+
+# This is the top-most .editorconfig file; do not search in parent directories.
+root = true
+
+# All files.
+[*]
+end_of_line = LF
+indent_style = space
+indent_size = 4
+charset = utf-8
+trim_trailing_whitespace = true
+insert_final_newline = true

.gitignore

@@ -2,3 +2,4 @@
 composer.lock
 composer.phar
 phpunit.xml
+.idea

.travis.yml

@@ -1,17 +1,32 @@
 language: php
 
 php:
-  - 5.3
-  - 5.4
-  - 5.5
   - 5.6
-  - hhvm
+  - 7.0
+  - 7.1
+  - 7.2
+  - 7.3
+
+# This triggers builds to run on the new TravisCI infrastructure.
+# See: http://docs.travis-ci.com/user/workers/container-based-infrastructure/
+sudo: false
+
+## Cache composer
+cache:
+  directories:
+    - $HOME/.composer/cache
+
+env:
+  global:
+    - setup=basic
 
 matrix:
-  allow_failures:
-    - php: hhvm
+  include:
+    - php: 5.6
+      env: setup=lowest
 
-before_script:
-  - composer install -n --dev --prefer-source
+install:
+  - if [[ $setup = 'basic' ]]; then travis_retry composer install --prefer-dist --no-interaction; fi
+  - if [[ $setup = 'lowest' ]]; then travis_retry composer update --prefer-dist --no-interaction --prefer-lowest --prefer-stable; fi
 
 script: vendor/bin/phpcs --standard=PSR2 src && vendor/bin/phpunit --coverage-text

README.md

@@ -11,32 +11,135 @@ processing library for PHP 5.3+. This package implements Authorize.Net support f
 
 ## Installation
 
-Omnipay is installed via [Composer](http://getcomposer.org/). To install, simply add it
-to your `composer.json` file:
-
-```json
-{
-    "require": {
-        "omnipay/authorizenet": "~2.0"
-    }
-}
-```
-
-And run composer to update your dependencies:
+Omnipay is installed via [Composer](http://getcomposer.org/). To install, simply require `league/omnipay` and `omnipay/authorizenet` with Composer:
 
-    $ curl -s http://getcomposer.org/installer | php
-    $ php composer.phar update
+```
+composer require league/omnipay omnipay/authorizenet:"3.x@dev"
+```
 
 ## Basic Usage
 
 The following gateways are provided by this package:
 
 * AuthorizeNet_AIM
+* AuthorizeNet_CIM
 * AuthorizeNet_SIM
+* AuthorizeNet_DPM
+
+In addition, `Accept.JS` is supported by the AIM driver and CIM (create card). More details are provided below.
 
 For general usage instructions, please see the main [Omnipay](https://github.com/thephpleague/omnipay)
 repository.
 
+## Accept.JS
+
+This gateway uses a JavaScript script to tokenize credit card details at the front end,
+i.e. in the payment form.
+Just the tokenized version of the credit card is then sent back to the merchant site,
+where it is used as a proxy for the credit card.
+
+The card is tokenized into two values returned in `opaqueData` object from Accept.JS:
+
+* dataDescriptor - the type of opaque data, e.g. "COMMON.ACCEPT.INAPP.PAYMENT"
+* dataValue - the value for the opaque data, e.g. "eyJjb2RlIjoiNT... {256 characters} ...idiI6IjEuMSJ9"
+
+These two values must be POSTed back to the merchant application, usually as a part of the payment form.
+Make sure the raw credit card details are NOT posted back to your site.
+How this is handled is beyond this short note, but examples are always welcomed in the documentation.
+
+On the server, the tokenized details are passed into the `payment` or `authorize` request object.
+You will still need to pass in the `CreditCard` object, as that contains details of the payee and
+recipient, but just leave the credit card details of that object blank. For example:
+
+```php
+// $gateway is an instantiation of the AIM driver.
+// $dataDescriptor and $dataValue come from the payment form at the front end.
+
+use Omnipay\Common\CreditCard;
+
+$request = $gateway->purchase(
+    [
+        'notifyUrl' => '...',
+        'amount' => $amount,
+        //
+        'opaqueDataDescriptor' => $dataDescriptor,
+        'opaqueDataValue' => $dataValue,
+        //
+        'card' => new CreditCard([
+            'firstName' => 'Anne',
+            'lastName' => 'Payee',
+            ...
+        ]),
+        ...
+    ]
+);
+```
+
+CIM Create Card feature usage:
+Accept.js must be implemented on your frontend payment form, once Accept.js 'tokenizes' the customer's 
+card, just send the two opaque fields and remove the Card's (Number, Expiration and CVV) from your post request.
+
+Accept.js goal is to remove the need of Card information from ever going into your server so be sure to remove that data
+before posting to your server.
+
+The create card feature on CIM will automatically create a Customer Profile and a Payment Profile with the 
+'tokenized' card for each customer you request it for on your authorize.net account, you can use these Payment Profiles 
+later to request payments from your customers.
+
+In order to create a Customer & Payment Profile pass the opaque fields and the card array with the billing information
+to the createCard method on the CIM driver:
+
+```php
+// $gateway is an instantiation of the CIM driver. //Omnipay::create( 'AuthorizeNet_CIM' )
+// $dataDescriptor and $dataValue come from the payment form at the front end.
+
+$request = $gateway->createCard(
+    [
+        'opaqueDataDescriptor' => $dataDescriptor,
+        'opaqueDataValue' => $dataValue,
+        'name' => $name,
+        'email' => $email, //Authorize.net will use the email to identify the CustomerProfile 
+        'customerType' => 'individual',
+        'customerId' => $user_customer_id,//a customer ID generated by your system or send null
+        'description' => 'MEMBER',//whichever description you wish to send
+        'forceCardUpdate' => true
+        'card' => [
+            'billingFirstName' => $name,
+            'billingLastName' => $last_name,
+            'billingAddress1' => $address,
+            'billingCity' => $city,
+            'billingState' => $state,
+            'billingPostcode' => $zipcode,
+            'billingPhone' => '',
+            //... may include shipping info but do not include card (number, cvv or expiration)
+        ],
+    ]
+);
+$response = $request->send();
+$data = $response->getData();
+
+$data['paymentProfile']['customerProfileId'];
+$data['paymentProfile']['customerPaymentProfileId'];
+
+// Now you can use these 2 fields to reference this customer and this payment profile for later use with 
+// the rest of the CIM driver features as usual.
+```
+
+## DPM and SIM Signatures
+
+DPM and SIM used to sign their requests with the `transactionKey` using the mdh HMAC algorithm.
+From early 2019, this algorithm is being removed completely.
+Instead, the SHA-512 HMAC algorithm is used to sign the DPM and SIM requests,
+and to validate the received  notifications.
+
+To start using the SHA-512 signing, set your `signatureKey` in the gateway:
+
+```php
+$gateway->setSignatureKey('48D2C629E4A...{100}...E7CA3C4E6CD7223D');
+```
+
+The `signatureKey` can be generated in the *API Credentials & Keys* section of your account setings.
+
 ## Support
 
 If you are having general issues with Omnipay, we suggest posting on

composer.json

@@ -28,14 +28,25 @@
         "psr-4": { "Omnipay\\AuthorizeNet\\" : "src/" }
     },
     "require": {
-        "omnipay/common": "~2.0"
+        "omnipay/common": "^3",
+        "ext-json": "*",
+        "ext-libxml": "*",
+        "ext-simplexml": "*"
     },
     "require-dev": {
-        "omnipay/tests": "~2.0"
+        "omnipay/tests": "^3",
+        "squizlabs/php_codesniffer": "^3",
+        "phpro/grumphp": "^0.14"
     },
     "extra": {
         "branch-alias": {
-            "dev-master": "2.0.x-dev"
+            "dev-master": "3.0.x-dev"
         }
-    }
+    },
+    "scripts": {
+        "test": "phpunit",
+        "check-style": "phpcs -p --standard=PSR2 src/",
+        "fix-style": "phpcbf -p --standard=PSR2 src/"
+    },
+    "prefer-stable": true
 }

grumphp.yml

@@ -0,0 +1,15 @@
+parameters:
+    git_dir: .
+    bin_dir: vendor/bin
+    tasks:
+        phpunit:
+            config_file: ~
+            testsuite: ~
+            group: []
+            always_execute: false
+        phpcs:
+            standard: PSR2
+            warning_severity: ~
+            ignore_patterns:
+              - tests/
+            triggered_by: [php]

phpunit.xml.dist

@@ -14,9 +14,6 @@
             <directory>./tests/</directory>
         </testsuite>
     </testsuites>
-    <listeners>
-        <listener class="Mockery\Adapter\Phpunit\TestListener" file="vendor/mockery/mockery/library/Mockery/Adapter/Phpunit/TestListener.php" />
-    </listeners>
     <filter>
         <whitelist>
             <directory>./src</directory>