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

Sequence number incorrect with api requests #60

Closed
jaykobi opened this issue May 2, 2017 · 2 comments
Closed

Sequence number incorrect with api requests #60

jaykobi opened this issue May 2, 2017 · 2 comments

Comments

@jaykobi
Copy link
Contributor

jaykobi commented May 2, 2017

The sequnce number is stored only in table "payone_protocol_transactionstatus". When an API request occurs this number is fetched and incremented for that request only. The incremented sequence number is not saved. Making two consecutive api requests fails because the second tries to use the same sequence number.

Example:

  1. Create order and have it paid.
  2. Create a credit memo for a partial amount of total recevivable => works.
  3. Create another credit memo for a partial amount => fails, wrong sequnce number.
@fjbender
Copy link
Contributor

fjbender commented May 2, 2017

Did you leave wait time between steps 2 and 3 to make sure the transaction status has been processed? That can take up to 15-20 minutes in test mode.

@jaykobi
Copy link
Contributor Author

jaykobi commented May 2, 2017

Nope, I did not. Sequence was number was incremented correctly with the callback!

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

No branches or pull requests

2 participants