Provide migration path from Veda's GoCardless
Created by: artfulrobot
Veda built what looks like an excellent extension for another bureau, SmartDebit, in their UK Direct Debit extension. Later they added in some minimal support for GoCardless. There were several technical reasons why it was necessary to start over with a new extension.
However it would be great to provide a migration (automated or by other instructions) so that people who have DDs set up using that can migrate over, benefiting from the automatic updates via webhook functionality.
The good news
Is that this extension should (not tested) automatically pick up and start filling out your database with Contributions for your Recurring Contributions set up with Veda's extension.
Payment processor/instrument
id/name of the payment processor and payment instrument. I'm not sure this really matters, but it probably should matter and might do one day.
Catchup
Anyone who has DDs set up through Veda's extension will have the situation that they have one Pending contribution against the DD. This extension will, on receiving a payment webhook will find this Pending contribution and will assume that this is the first payment on the DD and set the date accordingly. This might not be what you want, and anyway, hopefully you have contributions before this to back-fill.
trxn_id
on the initial Contribution is set to the subscription ID. This probably won't cause confusion except if anyone implements any further integration based on this extension's expectation that trxn_id
refers to a payment.
You can fix both of these by
- Remove the trxn_id from the Pending contribution (which might not be Pending any more if you've manually changed that).
- Do an import of payments to-date against the recurring payment (is this a standard feature of CiviCRM's import?)