Troubleshooting and FAQs

Common errors

The table below outlines common errors that may occur during account availability or ownership evaluation using Socure Account Intelligence (Standard or Premier). These issues can result from missing fields, input formatting problems, or module configuration. Understanding these patterns can help fine-tune workflows, reduce false positives, and determine when escalation or fallback logic is appropriate.

Issue	Explanation	Suggested fix
Missing or invalid `accountNumber` / `routingNumber`	Required bank account fields were not provided or failed basic validation.	Ensure both fields are present, numeric, and properly formatted before submission.
Unexpected `status_code` in enrichment block	A non-200 response indicates enrichment was not executed successfully.	Review the `status_code` and `response` fields. Retry if transient, otherwise open a support ticket.
Account Intelligence Premier not triggered	The `accountintelligencepremier` module was not called.	Confirm the `modules` array in the request included `"accountintelligencepremier"`.
Low `availabilityScore` despite valid account	External data sources may show conflicting signals on account status.	Confirm account details with the user. Escalate to review if the score is inconsistent with expectations.
Low `ownershipScore` with correct inputs	Provided name or entity did not align with bank records.	Validate `firstName`, `surName`, or `entityName`. Check for formatting errors (e.g., casing, spacing, suffix).
Ambiguous business vs. individual ownership	Request did not clearly specify whether account belongs to an individual or a business.	For businesses, include `entityName` and `ein`. For individuals, include `firstName`, `surName`, and `dob`.
Reason codes repeated (e.g., I998, I992–I994)	Multiple fallback signals may be returned.	Implement hierarchy or suppression logic to avoid duplicate handling of redundant reason codes.
Scores close to threshold (e.g., 0.50–0.70)	Probabilistic model generated uncertain signals.	Tune routing logic to treat mid-range scores as `REVIEW` instead of `PASS` or `FAIL`.

How to debug

To debug Account Intelligence Standard or Premier behavior in RiskOS™:

Use the eval_id to trace execution in the Developer Console or RiskOS logs.
Check the status_code in each data_enrichments[] block.
- A 200 indicates success.
- Any other status should be flagged.
Validate which enrichment modules were triggered. If Premier was expected but not called, confirm that required inputs were present:
```
"modules": ["accountintelligencepremier"]
```
Review reasonCodes for enrichment-level explanations (e.g., fallback logic, missing inputs, data mismatches).
Inspect account.availabilityScore and account.ownershipScore:
- High scores (≥ 0.90) indicate strong matches.
- Low scores (≤ 0.50) indicate weak or no correlation.
Confirm that sourceAttribution is present. Missing attribution may indicate insufficient coverage.

Fallback strategies

If Account Intelligence does not yield a confident result:

Retry with normalized inputs → Reformat account holder name, remove special characters, and ensure routingNumber follows ABA format.
Escalate to review → Use tags or review_queues to route uncertain results to human analysts.
Enable additional enrichments → Chain to other RiskOS modules (e.g., Document Verification or Watchlist) for additional confidence.
Accept partial matches in low-risk flows → For example, accept availability confirmation even if ownership is uncertain.

Escalation path

For production-impacting issues or debugging edge cases:

Reproduce the issue — Do this in sandbox or staging if possible.
Capture relevant identifiers — Collect:
- eval_id
- Full request payload
- referenceId from the Account Intelligence enrichment (if applicable)
Open a support ticket — you can email [email protected] for additional assistance or contact your Solutions Consultant team and include:
- Workflow name
- Input fields submitted
- Expected vs. actual decision
- Logs or screenshots (if applicable)
Urgent escalation — For high-severity cases, escalate via:
- Slack (if integrated)
- Your designated Socure escalation channel

Known issues

United States-only — Account Intelligence Standard and Premier are limited to U.S. accounts. They cannot be used in global flows.
Probabilistic scoring — Instead of binary yes/no, the system returns availabilityScore and ownershipScore on a 0–1 scale.
Reason code overload — Some transactions may return multiple fallback-related codes. Use a hierarchy or suppression logic.
Coverage gaps — Thin-file or recently opened accounts may return low confidence due to limited data source availability.
Special character normalization — Names or entity strings with diacritics/unicode may cause mismatches if not normalized.

📘
Note:
Use the Developer Console to view raw request/response logs in real time for debugging or validation.

FAQs

General product behavior

What is Socure Account Intelligence? What’s the difference between Standard and Premier?

Socure Account Intelligence (SAI) is a real-time service that verifies a bank account’s status (open/closed) and ownership.

Standard → Provides core availability and ownership scores using consortium and internal data.
Premier → Provides enhanced coverage and determinism through National Shared Databases, often with up to 20% higher coverage.

Who is eligible to use Account Intelligence Premier?

Eligibility is determined by industry, use case, regulator, and transaction volume.

High-risk businesses (e.g., online gambling, payday lenders) cannot access Premier and must use Standard.

To enable Premier, customers must complete the Early Warning® Reseller Payment Participant Application, which is reviewed by EWS/BNY Mellon. Approval is required before activation.

Why is Account Intelligence Premier not available for all clients or use cases?

Premier requires pass-through of National Shared Databases.

Regulatory, risk, and contractual constraints mean that:

Access is gated at the account/customer level.
Customers must be provisioned with a child ID.
Testing or POCs are forbidden until full onboarding and approval are complete.

Integration and input formatting

What is required technically to activate Account Intelligence Premier?

Customer must be provisioned in Socure’s system with a child ID for EWS integration.
After EWS approval, the API request must call the module:
```
"modules": ["accountintelligencepremier"]
```
Premier cannot be tested in sandbox without approval due to contractual restrictions.

How does the API request and response differ between Standard and Premier?

Request → Standard uses "accountintelligence". Premier uses "accountintelligencepremier".
Response → Both return identical output formats with availabilityScore, ownershipScore, and reasonCodes.
Internal config → Premier requires backend provisioning (child ID), but no extra fields are sent in the request.

What are common configuration or error issues with SAI Premier?

Child ID not set → Requests will fail if the customer is not properly configured.
Improper module name → Must use the exact spelling "accountintelligencepremier".
Unauthorized testing → Running Premier for unapproved clients or in sandbox is prohibited and may breach contracts.

Output and match interpretation

What scores and reason codes will I receive?

Ownership Score → [0.0 – 1.0] confidence that the account owner matches provided info.
Availability Score → [0.0 – 1.0] likelihood the account is open and active.
Reason Codes → Provide context on match results.

For unknown/no data, ownership may default to 0.40 or 0.68 depending on product version.

What if I see coverage issues or low scores?

Premier typically delivers ~20% higher coverage than Standard.
If Premier is enabled and gaps remain (e.g., certain sponsor banks), consult your Socure TAM.
Socure may investigate specific account ranges and provide workarounds.

Retry and fallback

What should I do if Account Intelligence does not yield a confident match?

Retry with normalized inputs (clean casing, spacing, remove special characters).
Escalate to REVIEW using tags or review queues for manual handling.
Use additional RiskOS enrichments (e.g., Document Verification, Watchlist).
In low-risk flows, accept availability confirmation even if ownership is uncertain.

Can I batch process Account Intelligence requests?

Yes, batch is supported but rate-limited.

Both Standard and Premier are typically capped at 20 TPS due to vendor restrictions.
For Premier, sandbox batch testing is not allowed without explicit EWS approval.

Debugging and escalation

How do I debug a failed enrichment or incomplete match?

Use eval_id to trace execution in the Developer Console.
Check status_code in each enrichment block (200 = success).
Confirm the correct module (accountintelligence vs accountintelligencepremier) was called.
Review reasonCodes for fallback, missing inputs, or mismatches.
Inspect availabilityScore and ownershipScore for confidence values.

When should I escalate?

Escalate when:

The enrichment module did not trigger despite valid input.
Scores are unexpectedly low for known-good identities.
Premier was expected but not activated.

Provide:

eval_id
referenceId (from enrichment response)
Workflow name
Full request/response payload
Reproduction steps and logs

Product limitations

Can I use Account Intelligence in global workflows?

Standard → U.S.-only, with limited consortium/internal data.
Premier → U.S.-only, requires National Shared Databases.

Neither module is FedRAMP-authorized or available in GovCloud environments.

Can I use Account Intelligence from the Admin Dashboard?

Standard → Supported from the Admin Dashboard.
Premier → Not currently supported from the dashboard (as of mid-2025). Must be integrated via API.

Is there a pricing difference between Standard and Premier?

Yes. Premier SKUs (Status & Ownership) are priced higher than Standard, reflecting higher coverage rates and vendor costs.

Contact your Socure account manager for details.

Who uses Account Intelligence and Premier?

Standard → Fintechs, e-commerce, lenders, payments platforms.
Premier → Banks, regulated industries, disbursement platforms, ACH fraud prevention, lending.

Premier is not available to high-risk industries (e.g., online gambling, payday lenders).

Can I use Verify+ in international workflows?

Not currently. Verify+ is strictly U.S.-only. For international coverage, use Verify (kyc) which supports 180+ countries.

Can I use this for document verification or selfie match?

No. Verify and Verify+ do not support document or biometric verification.

Use Socure Predictive DocV for ID document and facial biometric workflows.

Can I determine if someone is a politically exposed person (PEP)?

Not via Verify or Verify+.

Use the Watchlist module for sanctions screening, PEP detection, and adverse media checks.

How fresh are the data sources used?

Source freshness varies by type.

Some data (e.g., credit, government) updates daily, while others may update weekly.

You can inspect source types via sourceAttribution, but not individual source timestamps.