Error 2009 on the last step of registration

Vlad13Vlad13 Member Posts: 3
Hello. I wanted to create an account here on Payoneer but Error 2009 pops up just right on the last step of registration. I tried another browser but it didn't help. What could you advise? Thanks.

Comments

  • TalhaSaqibTalhaSaqib Member Posts: 7
    Hi,

    My bank account has been recently approved by Payoneer. However, when I am trying to link it with Fiverr (via 'Bank Transfer' option), I am having a technical issue on the Payoneer site.

    Upon clicking 'Bank Transfer', Fiverr redirects to Payoneer, where when I sign up, I am asked to add a new bank account. When I enter information about the bank and click submit. I get a 'General Error 2009'

    This error doesn't enlighten the actual issue, so it is unknown what is the problem. I have contacted Customer Support, however, as usual, they are taking too long to respond.

    Additional information: I previously used to use Payoneer MasterCard but now I have cancelled my card and trying to switch to bank transfer. Please note my bank is already approved by Payoneer.

    Can anyone please guide me? or look into my request. The request number is 200915-030103. There is a screenshot in my request as well for more clarity.

    Thank you.
  • laurel178laurel178 Member Posts: 1
    yo estoy tratando de crear mi cuenta y me sale este error como lo puedo resolver?
  • KazPayoneerKazPayoneer Confirm Email, Member, Administrator Posts: 1,566 ✭✭✭✭✭✭✭

    Hi there,

    This is a known issue that has been reported to our technical department. We hope to have a resolution soon, but it is being worked on.

    Thanks!

  • Vlad13Vlad13 Member Posts: 3
    Thanks, people! Somehow problem is solved now! B)
    I just installed Payoneer app from AppStore and made registration from there without any troubles. And before that i made a ticket which contained my issue and personal data, maybe that also helped.
  • KazPayoneerKazPayoneer Confirm Email, Member, Administrator Posts: 1,566 ✭✭✭✭✭✭✭

    Thanks for the update!

    I'm glad to say that this issue was resolved a couple of hours ago and you all should be able to proceed.

This discussion has been closed.