eDDA Troubleshooting Guide
About This Page
What: Complete troubleshooting workflow for eDDA authorization failures and eDDI Direct Debit failures, covering both the HSBC and Hang Seng channels Audience: Frontline customer service and Operations staff handling eDDA/eDDI tickets Prerequisites: eDDA Direct Debit Deposit — understand the eDDA/eDDI authorization and Direct Debit mechanism first Reading time: 8 minutes Owner: Deposit Operations Lead
Key takeaway: The first step in eDDA troubleshooting is always to identify the channel (HSBC or Hang Seng) — the two channels differ entirely in supported banks, authorization methods, and error handling. eDDA is for personal accounts only; corporate accounts are not supported.
Quick Navigation — What you might be looking for:
- Customer says authorization failed? → Channel Identification → HSBC Authorization Troubleshooting / Hang Seng Authorization Troubleshooting
- Customer says Direct Debit failed? → HSBC Direct Debit Troubleshooting / Hang Seng Direct Debit Troubleshooting
- Customer wants to unbind eDDA? → Unbinding eDDA
- Need to escalate? → Escalation Format
- Want to send the customer a help center link? → Help Center Links
Channel Identification
The first step in troubleshooting: determine whether the customer is using the HSBC channel or the Hang Seng channel.
eDDA Is for Personal Accounts Only
Corporate accounts do not support eDDA. If the customer has a corporate account, guide them to use other deposit methods.
Supported Banks Quick Reference
HSBC Channel Supported Banks (15)
| Bank | Onboarded |
|---|---|
| Hang Seng Bank | Initial |
| HSBC | Initial |
| Bank of China | 2021-06-17 |
| Nanyang Commercial Bank | 2021-07-27 |
| Fusion Bank | 2021-09-06 |
| ICBC Asia | 2021-09-07 |
| Standard Chartered | 2021-12-10 |
| ZA Bank | 2021-12-10 |
| CITIC Bank International | 2021-12-10 |
| Wing Lung Bank | 2021-12-10 |
| Airstar Bank | 2022-09-27 |
| CCB Asia | 2023-10-17 |
| LIVI BANK | 2024-01-25 |
| CMB | 2024-03-28 |
| Dah Sing Bank | 2024-03-28 |
Hang Seng Channel Exclusive Banks (5)
The following banks can only use eDDA via the Hang Seng channel and are not supported on the HSBC channel:
| Bank | Notes |
|---|---|
| Citibank | |
| Bank of East Asia | Watch out for the "daily single transaction" frequency trap |
| OCBC Wing Hang | |
| Chiyu Banking | |
| Bank of Communications HK | Requires in-branch application |
Banks Supported by Both Channels
The following 7 banks are supported on both the HSBC and Hang Seng channels. HSBC channel is recommended:
Hang Seng Bank, HSBC, Bank of China, Nanyang Commercial Bank, ICBC Asia, Standard Chartered, Wing Lung Bank
HSBC Channel Authorization Troubleshooting
Runbook: HSBC Channel Authorization Failure
Trigger: Customer initiates eDDA authorization within the Futu/moomoo App and receives an error Assessment: Identify the cause based on the error message (7 error types) Action: Handle according to the corresponding error type Verification: Customer re-authorizes successfully; "HSBC eDDA binding" is visible in CRM Bank Card Management
ID Document Types Supported by HSBC
| Document Type | Supported | Notes |
|---|---|---|
| Mainland China ID | Supported | |
| HK/Macau Travel Permit | Partially supported | Two-letter prefix permits are not supported → guide to Hang Seng channel |
| Hong Kong ID | Supported | |
| Passport | Supported | |
| Macau ID | Supported | Since 2024-06-06 |
7 Authorization Errors and Handling
| # | Error Message | Investigation Steps | Resolution |
|---|---|---|---|
| 1 | Account name does not match bank account ID document | First check: Does the customer hold a HK/Macau Travel Permit with a two-letter prefix (not supported)? | If yes → guide to Hang Seng channel; if no → contact bank to confirm account-opening document |
| 2 | Bank account number incorrect | Confirm the bank account number the customer entered | Re-enter the correct bank account number |
| 3 | Does not match mobile number registered with bank | — | Contact bank to confirm the registered mobile number |
| 4 | Bank account status abnormal | — | Contact bank to check account status |
| 5 | Bank account type abnormal | — | Contact bank to check account type |
| 6 | Bank account and name do not match | — | Contact bank to confirm account-opening name |
| 7 | Bank authorization error (no specific message) | All of the above ruled out | Guide customer to switch to Hang Seng channel |
Hang Seng Channel Authorization Troubleshooting
Runbook: Hang Seng Channel Authorization Failure
Trigger: Customer sets up Direct Debit authorization in the bank App but it has not taken effect Assessment: Confirm how long the customer has been waiting; verify the authorization form details Action: Handle based on wait time and correctness of form information Verification: "Hang Seng eDDA binding" record appears in CRM Bank Card Management
Authorization Form Requirements
When the customer sets up Direct Debit in the bank App, they must fill in the following:
| Field | Required Value |
|---|---|
| Bank | Select 024 Hang Seng Bank Limited |
| Account Number | 239772973001 |
| Account Name | FUTU SEC INTL HK LTD |
| Payer Reference | Customer's moomoo ID |
| Payment Account | Select an HKD account; ensure sufficient balance |
| Payment Limit | Recommend selecting No limit |
Authorization Details Must Be Accurate
Any incorrect field will cause authorization failure or Direct Debit anomalies. Pay special attention that the "Payer Reference" must be the customer's own moomoo ID.
Authorization Not Taking Effect
| Scenario | Resolution |
|---|---|
| Authorization submitted < 1 business day ago | Ask customer to wait; usually takes effect in 1-3 business days |
| Authorization submitted > 1 business day ago and still not effective | Verify each field on the authorization form |
| Bank has updated authorization info but Futu side has not synced | Auto-syncs after T+1 business day; Futu side cannot update directly |
When the Customer Says "I Did It in the Bank App" — Distinguishing eDDA from FPS
When a customer reports "deposit failed, I did it in the bank App", first determine whether it was eDDA authorization/Direct Debit or FPS transfer:
| Criterion | eDDA | FPS |
|---|---|---|
| Entry point | Bank App → "Direct Debit Management" or "Direct Debit Authorization" | Bank App → "Transfer" or "FPS Faster Payment" |
| Payee | FUTU SEC INTL HK LTD (authorization target) | Search for FPS ID (e.g. 1517622) |
| CRM record | Bank Account → Bank Account Authorization has an eDDA record | Deposit Funds → Pending has an FPS Bank Statement |
If confirmed as an FPS transfer rather than eDDA, handle per Deposit Troubleshooting — this page's workflow does not apply.
HSBC Channel Direct Debit Troubleshooting
Runbook: HSBC Channel Direct Debit Failure
Trigger: Customer initiates an eDDA deposit in the moomoo App but the Direct Debit does not succeed Assessment: First confirm where the customer performed the action (in-app vs bank App), then diagnose based on the combination of bank-side and Futu-side statuses Action: Handle based on the status combination Verification: Deposit credited / refund credited / customer is informed of next steps
Step 1: Confirm Where the Action Was Performed
Distinguish eDDA from FPS
When a customer says "deposit failed", first confirm where they performed the action:
- Performed within the moomoo App → This is an eDDA Direct Debit; continue with this troubleshooting flow
- Performed within the bank App → Most likely an FPS transfer, not eDDA; handle per the FPS workflow
Step 2: Diagnose by Status Combination
| Bank-Side Debit | Futu-Side Deposit | Cause & Resolution |
|---|---|---|
| Succeeded | Failed | Wait for automatic refund. If not refunded after 1 business day → escalate |
| Failed | Failed | See "HSBC Double Failure Investigation" below |
HSBC Double Failure Investigation
| Cause | Details | Resolution |
|---|---|---|
| Insufficient balance | HSBC defaults to debiting from savings account | Confirm savings account has sufficient balance |
| Frozen / unavailable funds | Fixed deposits, pledged funds, etc. | Contact bank to confirm fund status |
| Airstar Bank limit | Daily cap of HKD 500,000 | Split into multiple deposits or use another method |
All Methods Failed
If the customer repeatedly fails on the HSBC channel and the issue cannot be resolved → guide the customer to switch to the Hang Seng channel as a fallback.
Hang Seng Channel Direct Debit Troubleshooting
Runbook: Hang Seng Channel Direct Debit Failure
Trigger: Customer deposits via eDDA on the Hang Seng channel but the Direct Debit fails or the deposit does not credit Assessment: First check the error message, then diagnose based on the combination of bank-side and Futu-side statuses Action: Handle based on bank-specific rules Verification: Deposit credited / refund credited / customer has completed re-authorization
Diagnose by Status Combination
| Bank-Side Debit | Futu-Side Deposit | Cause & Resolution |
|---|---|---|
| — | Message: "Authorization info not yet effective / does not exist" | Authorization incomplete → guide customer to re-authorize |
| Succeeded | Failed | Wait for automatic refund. If not refunded after 1 business day → escalate |
| Failed | Failed | Investigate by the customer's bank (see below) |
Bank-Specific Investigation
Hang Seng Bank / HSBC
Account suffix 883 vs 001 issue
Hang Seng/HSBC account display rules:
- Current Account with suffix 883 → displays as 001 on the Futu side
- Savings Account with suffix 883 → displays as 883 on the Futu side
If the customer authorized with a current account but the suffix shown on the Futu side does not match, this rule may be the cause.
Bank of China (Hong Kong)
"One-off" Frequency Trap
If the customer set the transfer frequency to "One-off" during authorization, the authorization can only complete 1 eDDA transfer. From the 2nd attempt onward, the Direct Debit will inevitably fail.
Solution: Guide the customer to re-authorize. Refer to the help center link: https://help.futu5.com/faq/topic3009
Bank of East Asia / ICBC Asia
"Daily Single Transaction" Frequency Trap
The customer may have selected "single transaction per day" as the transaction frequency during authorization, which means only 1 eDDA deposit can be completed per day.
Solution:
- Cancel the existing authorization
- Re-authorize, selecting Per transaction + Unlimited payment count
Every Direct Debit Fails? Check the Remarks Field
If the customer's eDDA deposits at Bank of East Asia / ICBC Asia fail every time, check the Remarks / Debtor Reference field from the authorization — whether it contains lowercase letters or spaces. If so, re-authorize using the correct format.
Citibank
No known specific traps. Follow the standard workflow: verify authorization info → confirm sufficient balance → re-authorize.
OCBC Wing Hang
No known specific traps. Follow the standard workflow: verify authorization info → confirm sufficient balance → re-authorize.
Chiyu Banking
No known specific traps. Follow the standard workflow: verify authorization info → confirm sufficient balance → re-authorize.
Bank of Communications HK Branch
| Known Issue | Resolution |
|---|---|
| eDDA requires in-branch application | Bank of Communications does not support setting up eDDA Direct Debit via App/online banking. If the customer says "I can't find Direct Debit in the bank App" → this is expected; guide them to visit a branch with their ID |
| Authorization takes longer to activate | After in-branch application, it typically takes 3-5 business days to take effect on the Futu side (other banks usually take 1 business day) |
Hang Seng Channel Direct Debit Decision Tree
Unbinding eDDA
Runbook: eDDA Unbinding
Trigger: Customer requests to cancel eDDA authorization Assessment: Confirm the customer knows the unbinding method Action: Guide the customer to operate in the bank App Verification: Approximately 1 business day later, the binding record disappears from CRM Bank Card Management
eDDA unbinding can only be done by the customer on the bank side; Futu cannot unbind directly.
Steps:
- Customer logs in to the bank App/online banking
- Go to "Direct Debit Management"
- Find the Futu eDDA authorization and cancel/delete it
- Wait approximately 1 business day for the Futu side to auto-sync the cancellation
Escalation Format
When frontline staff cannot resolve the issue, contact @olegzhang via WeCom using the following format:
moomoo ID: xxxx
Channel: Hang Seng / HSBC
Customer's bank: xxxx
Issue type: eDDA authorization issue / eDDI Direct Debit issue
Description: xxxxxxxPre-Escalation Checklist
Before escalating, confirm the following investigation steps have been completed:
- Channel identified (HSBC / Hang Seng)
- Error message confirmed
- Troubleshooting performed per the corresponding scenario on this page
- Customer's moomoo ID and bank information collected
Help Center Links
When replying to customers, attach the corresponding help center tutorial link.
futuhk.com
| Bank | Link |
|---|---|
| HSBC | https://support.futuhk.com/topic631 |
| Hang Seng Bank | https://support.futuhk.com/topic630 |
| Bank of China | https://support.futuhk.com/topic47 |
| Nanyang Commercial Bank | https://support.futuhk.com/topic446 |
| ICBC Asia | https://support.futuhk.com/topic46 |
| Standard Chartered | https://support.futuhk.com/topic49 |
| Wing Lung Bank | https://support.futuhk.com/topic48 |
futufin.com
| Bank | Link |
|---|---|
| HSBC | https://www.futufin.com/cn/support/topic2_631 |
| Hang Seng Bank | https://www.futufin.com/cn/support/topic2_630 |
| Bank of China | https://www.futufin.com/cn/support/topic2_47 |
| Nanyang Commercial Bank | https://www.futufin.com/cn/support/topic2_446 |
| ICBC Asia | https://www.futufin.com/cn/support/topic2_46 |
| Standard Chartered | https://www.futufin.com/cn/support/topic2_49 |
| Wing Lung Bank | https://www.futufin.com/cn/support/topic2_48 |
Last Resort When All Methods Fail
When both the HSBC and Hang Seng channels have been investigated and the issue remains unresolved:
| Step | Action |
|---|---|
| 1 | Confirm whether the customer's bank is on the supported list (HSBC channel: 15 banks + Hang Seng channel: 5 exclusive banks) |
| 2 | Not on the list → The bank does not support eDDA. Guide the customer to use other deposit methods: FPS (near-instant, recommended) or online banking transfer |
| 3 | On the list but repeatedly failing → Contact @olegzhang using the Escalation Format with a complete investigation record |
| 4 | Inform the customer of the expected resolution time: typically 1-2 business days after escalation |
Recommended Alternative Deposit Methods
When eDDA is unavailable, recommend alternatives in this order:
- FPS (near-instant, simple to operate) — suitable for HKD deposits
- Online banking transfer (minutes to hours) — suitable for HKD/USD/CNH
- BST (Bank-Securities Transfer) (minutes) — only for customers already authorized with CMB/Minsheng/Airstar
After Reading
| I want to... | Go to |
|---|---|
| Understand the technical principles and protocol differences of eDDA/eDDI | eDDA Direct Debit Deposit |
| Troubleshoot other deposit issues (non-eDDA) | Deposit Troubleshooting |
| View the full deposit method overview and comparison | Deposit Methods Overview |
| Check bank capability matrix | Bank Capability Matrix |
| Look up error codes and status codes | Unified Error Code Center |
| Handle deposit Matching issues | Manual Matching Guide |