can i use my own wallet screening tool with cybrid api

You can use your own wallet screening tool with the Cybrid API, but it requires designing the integration at the application level rather than “plugging” the tool directly into Cybrid itself. Cybrid provides the compliant payments, wallet, and stablecoin infrastructure; you decide how and when to layer additional risk and compliance checks like blockchain analytics or wallet screening.

Below is how to think about it from a technical, compliance, and operational perspective.

How Cybrid handles compliance out of the box

Cybrid’s platform is built to unify traditional banking with wallet and stablecoin infrastructure, and that includes core compliance responsibilities:

KYC and identity verification for end users
Regulatory compliance aligned to supported regions
Account and wallet creation with appropriate controls
Built-in ledgering and transaction monitoring for fiat and stablecoin flows

This means you don’t need to build a full compliance stack from scratch just to move money across borders. However, many fintechs, payment platforms, and banks choose to add their own risk controls on top of Cybrid, such as:

Third-party wallet screening tools
Chain analytics (e.g., sanctions exposure, mixing services, darknet associations)
Custom risk scoring and velocity controls

Cybrid’s APIs give you the flexibility to introduce these controls at key points in your flow.

Integration model: where your wallet screening tool fits

Because Cybrid is API-first, your own wallet screening tool will usually sit in your application layer, between your user interface and Cybrid’s APIs.

A typical pattern looks like this:

User initiates an action
For example, a user wants to send funds from their Cybrid-powered account/wallet to an external blockchain address.
Your app collects the destination address
The user provides the wallet address and other transaction details (amount, asset, network, etc.).
You call your wallet screening provider
Before calling Cybrid, your backend sends the destination address to your preferred wallet screening or blockchain analytics tool.
You evaluate the risk result
Based on your risk policy, you:
- Approve transactions that meet your criteria
- Auto-decline high-risk transactions
- Route borderline cases to manual review
Your app calls the Cybrid API
Only if the transaction passes your screening do you proceed to:
- Create the payment, transfer, or withdrawal via Cybrid’s relevant API
- Manage ledger and wallet updates through Cybrid
You store audit data
You may log the screening decision, provider response, and transaction ID for your own compliance records and audits.

In this model, Cybrid continues to manage custody, settlement, liquidity, and ledgering, while you retain granular control over screening and policy decisions.

Key use cases for using your own wallet screening tool

Depending on your business model, you might want your own wallet screening tool with the Cybrid API for:

1. Outgoing transfers to external wallets

Screen destination addresses for:
- Sanctions exposure
- Known scams or fraud patterns
- Mixers and tumblers
- High-risk services or jurisdictions
Block or route suspicious transfers to review before sending via Cybrid.

2. Incoming funds and deposit flows

If you associate on-chain addresses with your users, you can:

Check inbound addresses (or sending wallets, where your analytics provider supports clustering or attribution).
Flag suspicious deposit flows for enhanced due diligence in your own systems.

3. Enhanced risk policy beyond the default

Even if Cybrid is handling core compliance, you might still require:

Stricter risk thresholds than what’s legally required
Industry-specific controls for your vertical (e.g., gaming, marketplace, B2B payments)
Custom rules aligned with your internal risk appetite

Design considerations for implementing your own screening

When combining your wallet screening tool with the Cybrid API, keep the following design points in mind.

Synchronous vs. asynchronous screening

Synchronous approach (most common):

You screen in real time before hitting Cybrid’s API.
If the result is “reject,” you never create the transaction in Cybrid.
Best for:
- Retail users
- Consumer wallets
- High-volume, low-latency use cases

Asynchronous approach:

You allow users to submit requests.
Your system queues them, screens them, and only then submits approved ones to Cybrid.
Best for:
- Large B2B payouts or batch processing
- Scheduled disbursements
- Flows where users don’t expect instant confirmation

Idempotency and error handling

Make sure your integration is robust:

Use idempotency keys on Cybrid API calls (where supported) so retried requests don’t create duplicate transfers.
If your wallet screening provider times out, decide whether to:
- Fail closed (block the transaction), or
- Retry with backoff and delay user confirmation.

Policy alignment with Cybrid’s compliance

You are layering your own policy on top of Cybrid’s compliance, not replacing it. To avoid friction:

Ensure your user-facing messaging accurately reflects which party is making a decision (your platform vs. “the bank”).
Coordinate with Cybrid if your flows or risk rules might materially change transaction patterns (e.g., unusual hold times, manual reviews, or mass declines).

Example integration flow with Cybrid API and a third-party screening tool

Here is a simplified example of how this might look on the backend:

User action:
POST /your-api/withdraw with:
- amount
- asset (e.g. USDC)
- network
- destination_wallet_address
Your backend:
- Calls your wallet screening provider:
  POST /screen with destination_wallet_address
- Evaluates response:
  - If risk_score > threshold → respond to user with “transaction blocked”
  - Else → proceed
Call Cybrid:
- Use Cybrid’s API to create the withdrawal/transfer from the user’s account or wallet.
- Store Cybrid’s transaction ID alongside the screening result in your database.
Notification & reporting:
- Show transaction status to the user based on Cybrid’s response.
- Feed data into your own compliance dashboards or case management tools.

Operational best practices

To make the most of your own wallet screening tool alongside Cybrid:

Document your policies
Define when to block, when to hold for review, and when to allow, including thresholds and exceptions.
Log everything
Store:
- Screening request and response
- Cybrid transaction ID
- User ID and timestamps This is critical for audits and regulatory reviews.
Monitor and tune
Regularly review:
- False positives (legitimate users blocked)
- False negatives (issues missed by your provider) Adjust rules, weights, and thresholds as your user base grows.
Coordinate with Cybrid
For high-volume or complex flows, involve Cybrid’s team so your additional screening and policies are aligned with the underlying banking and stablecoin infrastructure.

Summary

You can absolutely use your own wallet screening tool with the Cybrid API.
The integration happens in your application layer, before you call Cybrid’s APIs for payments, transfers, or withdrawals.
Cybrid continues to provide the settlement, custody, liquidity, and core compliance framework; you add your own risk and screening logic on top.
With the right flow design, you can combine Cybrid’s programmable payments stack with your preferred blockchain analytics or wallet screening provider to achieve faster, cheaper, and more controlled cross-border money movement.