CiviCRM Community Forums (archive)

We're currently storing iATS customer codes (tokens for recurring contributions) in a separate table [and link them to the contribution_recur table] - but are thinking it would be nice to pull all things recurring together in one table -> the CiviCRM core contribution_recur one. It contains a field - that could potentially be appropriate to store tokens:

12 processor_id varchar(255) utf8_unicode_ci Yes NULL
Description: "Possibly needed to store a unique identifier for this recurring payment order - if this is available from the processor??"

I can see some data in that processor_id field for my projects that have historic PayPal contributions - though all values appear to be identical to adjacent column: trxn_id - does anyone know of anyone/any application using this processor_id?

Perhaps processor_id could be recycled -> re-designated to: token? This contribution_recur table seems to be the most logical place to store tokens - many payment processors are using tokens these days - they need to be stored somewhere in the CiviCRM database - and rather than storing them with individual payment processor tables - perhaps we could designate a spot in a contribution_recur table [either recycling or adding]?