Add support for recurring options to first_pay gateway

Follow

David Hart

May 22, 2018 15:10

We are getting ready to do the majority of our processing against the first_pay gateway.  It would dramatically improve and simplify life for us if you could add support for these gateway specific fields:

• recurring
• recurringStartDate
• recurringEndDate

The documentation for these attributes is at http://support.1stpaygateway.net/gateway/Docs/API/Transactions/Sale.html

 

0

• 

  Permanently deleted user May 22, 2018 20:23

  Hi David,

  Thanks for submitting this request!

  While you do mention that this would be a significant quality of life improvement, can you confirm that you're still able to submit recurring transactions through First Pay without these fields? 

  I want to make sure that you're not blocked on transactions while we work to implement these fields.

  Thanks!

  Branden

  0

  Comment actions Permalink
• 

  David Hart May 22, 2018 21:29

  First of all, thanks for responding so quickly.  I wasn't sure if this was really an effective mechanism for making a feature request.

  I'm not sure that I understand what you are asking though.  I don't think that we can submit the recurring transactions unless you support passing the data via the gateway_specific_fields, or is there a way for me to pass arbitrary data through to the gateway?  I am just submitting the transaction via a purchase API call through Spreedly, and don't keep credentials that I could use to access First Pay directly within our system .

  For some more background, we currently support recurring transactions (donations in the case of our business model) only if the gateway has an internal scheduling mechanism (like subscriptions in Stripe).  Longer term, I plan on handling the scheduling internally using tokens stored in Spreedly and your card updater service, but in the interim I would like to be able to use the scheduling built into First Pay as a pressure relief valve so that there is less urgency around building out our internal scheduler.

   

  1

  Comment actions Permalink
• 

  Permanently deleted user May 22, 2018 23:46

  Thanks for providing those additional details. That definitely makes sense.

  These would need to be added as gateway specifics fields before they can be passed to the gateway.

  My question was in regards to First Pay allowing subsequent payments without the use of a CVV. For many gateways, passing a `recurring` flag is the only way to allow purchase transactions to be processed without a CVV.  It appears that this is the case here.

  0

  Comment actions Permalink

Please sign in to leave a comment.