Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make an effort to use unique transaction IDs. #27

Closed

Conversation

xurizaemon
Copy link
Contributor

Refs #26

@eileenmcnaughton
Copy link
Owner

My current thinking around this is that I will add (at some point) a civicrm_payment table via this extension & track all payments that way & hold a field within that table to represent the value passed to the payment processor. At that point the return value can be more flexible & I expect to use some sort of template

@xurizaemon
Copy link
Contributor Author

Sounds like a good plan. But not Smarty for the template, ok? :D

I believe we identified a core processor affected by the same - in 🚌 currently so can't check - which makes me wonder if there fix needs to go there instead of in an extension?

@eileenmcnaughton
Copy link
Owner

I seek to conquer all & replace core processors :-)

Your request for smarty is noted...

@eileenmcnaughton
Copy link
Owner

Closing this - I want to go down the path of pre-fixing & if really necessary templating rather than randomising

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants