Samsung Pay - Unknown error by ErrorCallback

[davekr]

I just got my AT&T S7 Edge today and I was going to try registering for Samsung Pay so I could get the free wireless charger. However, when I get to the "Verification method" screen and click on "Use Fingerprint" I get an error message that says "Unknown error by ErrorCallback". Clicking OK brings me back to the Verification method screen. The other option on that page says "Skip and use Samsung Pay PIN". Clicking this does nothing at all. Has anyone run into this problem? Any ideas how I might get around this?

 

[optimummind]

Reboot phone, open Galaxy Apps, and look for an update to the Samsung Pay framework app. After installing that update, i was able to proceed & add my cards and have fingerprint work.

Sprint GS7E.

 

[davekr]

I looked in Galaxy Apps and I'm not able to find a Samsung Pay framework app anywhere. When I first launched Samsung Pay it told me there was an update so I did that but I have had this problem since then. I trued removing the update but when I launch the original version it just makes me update to the newer one again.

 

[davekr]

Follow up on this issue:

I called Samsung yesterday and they told me the reason it wasn't working is because Samsung Pay isn't supported on this phone yet. They said it would be enabled on March 11 since that is the official release date. Okay, fair enough. While I think it is ridiculous to allow a phone to be released a few days early with software that is broken at the time (horrible user experience), if this were true I'd live with it.

This morning (March 11) I woke up and was pleasantly surprised to see that both Samsung Pay and something that seemed to be Samsung Pay Framework (it had an abbreviated name that I don't remember now) had updates available in the Galaxy Apps store. I updated both of them and guess what? Same error!!! I'm sorry, but there is no excuse for this. Samsung Pay is one of their key differentiating features. They should make sure that it is working properly on all carrier variants.

 

[testt]

Follow up on this issue:

I called Samsung yesterday and they told me the reason it wasn't working is because Samsung Pay isn't supported on this phone yet. They said it would be enabled on March 11 since that is the official release date. Okay, fair enough. While I think it is ridiculous to allow a phone to be released a few days early with software that is broken at the time (horrible user experience), if this were true I'd live with it.

This morning (March 11) I woke up and was pleasantly surprised to see that both Samsung Pay and something that seemed to be Samsung Pay Framework (it had an abbreviated name that I don't remember now) had updates available in the Galaxy Apps store. I updated both of them and guess what? Same error!!! I'm sorry, but there is no excuse for this. Samsung Pay is one of their key differentiating features. They should make sure that it is working properly on all carrier variants.

Did you change your DPI? I set mine to 520 and received this error and corrected it by setting it to 560, which is a DPI that Samsung supports.

 

[davekr]

Did you change your DPI? I set mine to 520 and received this error and corrected it by setting it to 560, which is a DPI that Samsung supports.

Wow, good call. I never would have associated the 2 things. I have my DPI set to 500. I noticed that the camera app got a little strange when I had the DPI lower than 500 but everything else had been working perfectly so that didn't even cross my mind. Thanks testt!!

 

[rockyjay]

Wow, good call. I never would have associated the 2 things. I have my DPI set to 500. I noticed that the camera app got a little strange when I had the DPI lower than 500 but everything else had been working perfectly so that didn't even cross my mind. Thanks testt!!

I'm replying to this thread because I ran into this issue today. Prior to using the app, it had me do an update from within the app. I'm not sure it that was the issue, but even after will the cache it still didn't work. Finally after finding the app in the Play store, I uninstalled the update, then reinstalled it from the Play store rather than from within the app. That seemed to fix the log in issue for me.