FAB Merchant Onboarding: Auto-created Hyperwallet account stuck in pending activation, workflow dead-end

Hi Epic FAB Team,

I am a company merchant completing FAB onboarding. All prior steps are fully approved: agreement, publisher profile, creator code, merchant identity, tax setup have all passed review.I am a company merchant completing FAB onboarding. All prior steps are fully approved: agreement, publisher profile, creator code, merchant identity, tax setup have all passed review.I am a company merchant completing FAB onboarding. All prior steps are fully approved: agreement, publisher profile, creator code, merchant identity, tax setup have all passed review.I am a company merchant completing FAB onboarding. All prior steps are fully approved: agreement, publisher profile, creator code, merchant identity, tax setup have all passed review.

At the final payment setup step, the FAB onboarding system automatically created a second separate Hyperwallet account for my company. This auto-generated Hyperwallet account is locked and pending activation.At the final payment setup step, the FAB onboarding system automatically created a second separate Hyperwallet account for my company. This auto-generated Hyperwallet account is locked and pending activation.At the final payment setup step, the FAB onboarding system automatically created a second separate Hyperwallet account for my company. This auto-generated Hyperwallet account is locked and pending activation.At the final payment setup step, the FAB onboarding system automatically created a second separate Hyperwallet account for my company. This auto-generated Hyperwallet account is locked and pending activation.

The core workflow problem:The core workflow problem:The core workflow problem:The core workflow problem:

  1. This FAB-generated Hyperwallet account cannot be located by Hyperwallet support when searching by its account ID alone, because the account has not been activated.
  2. I already have a fully activated Hyperwallet account under the same Epic organization for Epic Developer Portal, with all company documents and tax information verified and approved. My company entity is fully validated.
  3. FAB support cannot operate or activate the Hyperwallet account, while Hyperwallet frontline support cannot locate this pending account without the correct lookup method. There is no built-in pathway inside FAB to complete activation of this auto-created Hyperwallet account.

This system design creates a dead end for merchants. All compliance checks are finished, but merchants get stuck on the final payment step, with no self-service way to activate the auto-generated Hyperwallet account. It consumes massive time and effort for FAB merchants.This system design creates a dead end for merchants. All compliance checks are finished, but merchants get stuck on the final payment step, with no self-service way to activate the auto-generated Hyperwallet account. It consumes massive time and effort for FAB merchants.This system design creates a dead end for merchants. All compliance checks are finished, but merchants get stuck on the final payment step, with no self-service way to activate the auto-generated Hyperwallet account. It consumes massive time and effort for FAB merchants.This system design creates a dead end for merchants. All compliance checks are finished, but merchants get stuck on the final payment step, with no self-service way to activate the auto-generated Hyperwallet account. It consumes massive time and effort for FAB merchants.

I want to report this workflow defect and ask if there is a standard procedure to activate this automatically created pending Hyperwallet account for FAB merchants.I want to report this workflow defect and ask if there is a standard procedure to activate this automatically created pending Hyperwallet account for FAB merchants.I want to report this workflow defect and ask if there is a standard procedure to activate this automatically created pending Hyperwallet account for FAB merchants.I want to report this workflow defect and ask if there is a standard procedure to activate this automatically created pending Hyperwallet account for FAB merchants.

Epic Company ID: c-7f93fd80db463eb63bfb7f726c5108Epic Company ID: c-7f93fd80db463eb63bfb7f726c5108Epic Company ID: c-7f93fd80db463eb63bfb7f726c5108Epic Company ID: c-7f93fd80db463eb63bfb7f726c5108

Thank you.Thank you.Thank you.Thank you.

We would be happy to look into this for you! Please reach out to our support team using this link here.

Re:(26861464) Subject:Urgent: Cannot complete FAB merchant onboarding — stuck at payout setup step 6

Hello FAB Support Team,

I am writing regarding my FAB publisher onboarding process. My tax information has been fully verified, but I encountered a block at the payout setup stage. A Hyperwallet merchant account automatically generated by the FAB workflow has been suspended.

I have spent two weeks following up on this issue through the Epic Developer Portal ticket and direct phone calls to Hyperwallet. When I called Hyperwallet myself, their support agent was unable to locate this FAB-generated Hyperwallet account ID. The Developer Portal support channel has reached the limit of available escalation paths.

Primary Request: My existing Hyperwallet account connected to the Epic Developer Portal is fully KYC verified, activated and works normally. I would like to request if FAB backend can link this FAB publisher profile to my existing, operational Hyperwallet account from Developer Portal. This will avoid generating a brand-new separate Hyperwallet merchant account for FAB. The root cause of the suspension is that the same business entity ends up with two Hyperwallet accounts, triggering Hyperwallet anti-money-laundering risk control rules. Reusing the existing approved Hyperwallet account can resolve this fundamentally.

Backup Request (if cross-system account linking is technically impossible): If FAB system architecture cannot bind to the existing Developer Portal Hyperwallet account, please escalate this ticket to the FAB Finance & Compliance team. Ask FAB Finance & Compliance to liaise directly with the Hyperwallet risk team, and clearly explain: this suspended Hyperwallet account is automatically created by mandatory FAB publisher onboarding requirement, it is not manually created or registered by me. Both Developer Portal and FAB ticket records have confirmed this FAB built-in rule. Please request Hyperwallet risk team to conduct manual review and lift the suspended restriction of this account.

Attached screenshots for reference:

1. Screenshot of my FAB tax setup page showing tax information successfully verified.

2. Screenshot from Epic Developer Portal support ticket showing my two-week follow-up of the Hyperwallet account issue.

3. Screenshot showing my Developer Portal Hyperwallet account status (active and fully verified).

Please help escalate this case accordingly. Let me know if you require any further documents or information.

May I also confirm with the FAB team: given the current situation, does this mean I will be unable to complete the FAB marketplace onboarding and offer my original high-quality AAA game assets to global users?

Please refer to my attached screenshots.

Best regards, [Shuangyan Zhang]

FAB Publisher ID: [ 4397ca4558b949e6a0571a39e36acf8b ]