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

Refunds not appearing in izettle dashboard #13

Closed
mmartinmendez opened this issue Nov 20, 2020 · 6 comments
Closed

Refunds not appearing in izettle dashboard #13

mmartinmendez opened this issue Nov 20, 2020 · 6 comments

Comments

@mmartinmendez
Copy link

Expected Behavior

The refunds appear in the izettle dashboard.

Current Behavior

The refund is successful but the transaction is not shown in the izettle dashboard.

Context

  • Operating Version: Android version 9
  • SDK version: 1.8.9
@fabriciovergara
Copy link
Contributor

fabriciovergara commented Nov 25, 2020

@dmilovanovi can you follow up this one please?

@mmartinmendez
Copy link
Author

When logging the response from the sdk it says the refund was successful. To confirm i made the same refund a second time for which the response was that the refund was already performed. This is reflected with the refund appearing in the account in 2-3 days. The only part of the flow that is not working is the refund transaction/log not appearing in the dashboard when i sign into izettle. I use the sdk from ios as well and here the refund transaction logs appear immediately in the dashboard.

@ssikira
Copy link

ssikira commented Nov 26, 2020

Hello @mmartinmendez! Just to confirm, you don't see refunds in the iZettle Back Office (my.izettle.com) if you perform a refund through the iOS SDK?

@mmartinmendez
Copy link
Author

Hi @said-iz, I do see it through the ios sdk. I dont see it when i use the android sdk.

@ssikira
Copy link

ssikira commented Nov 26, 2020

@mmartinmendez thanks. We'll take a look and let you know 👍

@bobzettle
Copy link
Contributor

Apologies for not getting back to you earlier. We have released a fix for the reported issue, but would recommend you to update the SDK to the latest version.
You can view all the SDK releases here.
Feel free to open a new case if the issue is still present or you require further assistance.

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

4 participants