-
Notifications
You must be signed in to change notification settings - Fork 69
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
Transaction records should be created upon first POST #22
Labels
bug
Something isn't working
Comments
This will be released as a part of the Form Integrations functionality #27 |
JakeUrban
added a commit
to JakeUrban/django-polaris
that referenced
this issue
Dec 4, 2019
JakeUrban
added a commit
to JakeUrban/django-polaris
that referenced
this issue
Dec 4, 2019
JakeUrban
added a commit
to JakeUrban/django-polaris
that referenced
this issue
Dec 4, 2019
JakeUrban
added a commit
to JakeUrban/django-polaris
that referenced
this issue
Dec 4, 2019
JakeUrban
added a commit
to JakeUrban/django-polaris
that referenced
this issue
Dec 5, 2019
JakeUrban
added a commit
to JakeUrban/django-polaris
that referenced
this issue
Dec 6, 2019
JakeUrban
added a commit
to JakeUrban/django-polaris
that referenced
this issue
Dec 6, 2019
Released with 0.9.8 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When a client POSTs to
/transaction/withdraw/interactive
or/transaction/deposit/interactive
it should create a persisted Transaction object to the db. Currently we create an ephemeral UUID, and then upon submission of the interactive webapp we use that UUID to actually create a Transaction object. The problem here is that since there's no record, the/transactions
endpoint is empty so it looks like no transaction has been started. It's even more confusing since the transaction originally returned does have an ID so it seems like we should be able to query it, but can't.The text was updated successfully, but these errors were encountered: