mlutfy / au.com.agileware.ewayrecurring Goto Github PK

CiviCRM payment processor extension for eWay which uses the latest eWay Rapid API and ensures PCI DSS compliance.

Supports both once-off and recurring payment utilising the secure token payment method. This essential for automating the process setting up recurring donations and memberships in your CiviCRM securely and reliably. This payment processor also allows you to specify a particular day of the month to process all recurring payments together.

You will need to have an eWay account to use this payment processor on your CiviCRM website.

1. Download the latest version of this extension
2. Extract it to your CiviCRM extensions directory, as defined in "System Settings / Directories".
3. Go to "Administer / System Settings / Extensions" and enable the "eWay Recurring Payment Processor (au.com.agileware.ewayrecurring)" extension.
4. Configure the payment processor with your eWay API Key and Password as obtained from your eWay Account. eWay provides step by step instructions for generating these details.

The eWay Transaction Verifications job verifies the pending transactions in eway. This is required for when CiviCRM is unable to verify the transaction immediately, for example if the end user does not press the Return to Merchant button or if the contribution was made via a Drupal Webform.

Visit civicrm/admin/job to enable eWay Transaction Verifications job.

Recurring contribution transactions could fail for one of several reasons; in these situations, the extension will mark the recurring contribution as failed and retry the transaction at an interval up to a maximum number of times, both of which can be configured.

To update the Maximum retries and Retry delay (in days) go to civicrm/ewayrecurring/settings. The default Maximum retries is 3 and Retry delay is 4 days.

This extension applies changes to the following CiviCRM templates:

1. CancelSubscription - hides an option to send cancellation request, as all processing is done locally
2. Amount - adds a field to specify the day for recurring payment in the contribution page settings
3. UpdateSubscription - adds a field to change the next payment date

The 2.0.0 version introduces use of the eWay RapidAPI 3.1, which requires a different method of authentication with eWay from that used in the 1.x series.

You will need to Download and extract the extension as usual, and after running the Extensions upgrades, you will need to generate an API Key and Password as above and update these details in your Payment Processor settings.

Once your authentication details are updated, existing recurring payments will continue to operate as usual.

This CiviCRM extension was developed by the team at Agileware.

Agileware provide a range of CiviCRM services including:

• CiviCRM migration
• CiviCRM integration
• CiviCRM extension development
• CiviCRM support
• CiviCRM hosting
• CiviCRM remote training services

Support your Australian CiviCRM developers, contact Agileware today!