Talk:Fundraising system spec: Difference between revisions
Jump to navigation
Jump to search
(→Gift aid & payment processing: aha!) |
No edit summary |
||
Line 16: | Line 16: | ||
:In the past we've used a manual process for CiviCRM integration which involved downloading a file of all transactions from Paypal and SmartDebit every so often, playing with it in Excel, and uploading a CSV file to SmartDebit. The Gift Aid and Data Protection tickboxes are handled as follows: for Paypal, they are passed to the payment processor along with the other payment information, and end up in a "custom number" field in the Paypal back end. For SmartDebit we create a reference number with each transaction that is begun, and record against it the GA and DP status in an HTML table. The reference number is passed to the payment processor and the GA/DP status is then manually looked up in the table before the Smartdebit file is uploaded to Civi. [[User:The Land|The Land]] ([[User talk:The Land|talk]]) 21:06, 22 August 2012 (UTC) | :In the past we've used a manual process for CiviCRM integration which involved downloading a file of all transactions from Paypal and SmartDebit every so often, playing with it in Excel, and uploading a CSV file to SmartDebit. The Gift Aid and Data Protection tickboxes are handled as follows: for Paypal, they are passed to the payment processor along with the other payment information, and end up in a "custom number" field in the Paypal back end. For SmartDebit we create a reference number with each transaction that is begun, and record against it the GA and DP status in an HTML table. The reference number is passed to the payment processor and the GA/DP status is then manually looked up in the table before the Smartdebit file is uploaded to Civi. [[User:The Land|The Land]] ([[User talk:The Land|talk]]) 21:06, 22 August 2012 (UTC) | ||
::Ouch :P I see why you want something more integrated! :) --[[User:ErrantX|ErrantX]] ([[User talk:ErrantX|talk]]) 21:14, 22 August 2012 (UTC) | ::Ouch :P I see why you want something more integrated! :) --[[User:ErrantX|ErrantX]] ([[User talk:ErrantX|talk]]) 21:14, 22 August 2012 (UTC) | ||
== Code Rights == | |||
Will the code developed as a part of this contract be released as open source? | |||
[[Special:Contributions/115.114.59.182|115.114.59.182]] 11:27, 6 September 2012 (UTC) |
Revision as of 12:27, 6 September 2012
Do we have anything currently working? or is this all a "start from scratch" thing. --ErrantX (talk) 20:24, 22 August 2012 (UTC)
Gift aid & payment processing
Ok, so rather than clog up the main page too much.. here's an outline flow
- Collecting "yes to gift aid" is simple enough. Taking the Paypal API as an example (the other API is unknown at this point - we probably need to get that information from SmartDebit) you generally, depending on the preffered flow, ping Paypal to request a redirect url & transaction ID.
- Gift aid preference and transaction ID could be pushed into a queue (i'd use something high availability like resque or something) and the user directed to the gateway
- Gateway sends them back, after payment, to a thank you page (along with transaction id). This triggers a (background) query the for further details (name, address, current status of payment etc.) which are added to the queue
- Depending on the API's being used:
- Once payments are validated the gateway pings us with the transaction ID, a worker grabs the relevant queue entry and updates CiviCRM
- A background job regularly checks queue entries for their status (via the gateway API) & pushes them to CiviCRM as appropriate
This needs a lot of refinement but should work. I am not sure what we used in the past?? --ErrantX (talk) 20:56, 22 August 2012 (UTC)
- In the past we've used a manual process for CiviCRM integration which involved downloading a file of all transactions from Paypal and SmartDebit every so often, playing with it in Excel, and uploading a CSV file to SmartDebit. The Gift Aid and Data Protection tickboxes are handled as follows: for Paypal, they are passed to the payment processor along with the other payment information, and end up in a "custom number" field in the Paypal back end. For SmartDebit we create a reference number with each transaction that is begun, and record against it the GA and DP status in an HTML table. The reference number is passed to the payment processor and the GA/DP status is then manually looked up in the table before the Smartdebit file is uploaded to Civi. The Land (talk) 21:06, 22 August 2012 (UTC)
Code Rights
Will the code developed as a part of this contract be released as open source? 115.114.59.182 11:27, 6 September 2012 (UTC)