Subscription IDs and how they are stored

[stirton]

Hi guys,

 

Hoping someone can maybe help here.

 

We are finding that subscriptions are stored against each individual product, and therefore any pre-auth done gets a 'token' back and that is saved so that future invoices can be taken against the subscription.

 

Looking specifically at GoCardless but this may apply to other gateway modules? where we don't wish to have user interaction AFTER the first pre-auth has been granted. I mean, who wants to have to 'approve' each product for payment (from a user point of view)?

 

What I was thinking was to store subscription info against a customer rather than a product and then use that with the gateway, however I don't think we can due to most of the code 'looking ahead' during a cron run will automatically point to the product subscription field.

 

Thoughts on how to best over come this.

As mentioned, this has been sparked by us looking at the GoCardless integration and I need to next look at our c/card payment gateway provider and how it works too.

 

Thanks

Neil