Skip to content

    STUPORE / FOUR PLATFORMS. ONE ECOSYSTEM.

    A complex world.
    A clearer perspective.

    Respond to incidents. Read the markets. Govern your agents. Build what comes next.

    CHOOSE YOUR STARTING POINT ↓

    WHY CRYPTODAM · PATENTS & MARKET EVIDENCE

    Safeguarding and restoring trust in crypto and stablecoins.

    Designing investor protection since 2024. Recurring incidents show why it matters.

    1. Observe
    2. Verify
    3. Review
    Illustrative protection workflow

    A sculpted brass dam crosses fine teal signal lines beside orderly evidence records, illustrating an intended observation, verification and review process.

    CryptoDam — Crypto & Stablecoin Insurtech Insurance Platform

    CryptoDam is building investor protection on patented technology, with clear protection terms, verifiable incident evidence, and accountable compensation processes. Our mission is to safeguard investors and help rebuild trust in crypto and stablecoin markets—in Korea and worldwide.

    01 / DOCUMENTED FOUNDATION

    A documented starting point.

    The founder’s patent records describe a technical approach to risk assessment, premium calculation, multi-source trigger verification and compensation processes.

    Patent records do not establish insurance authorization, government endorsement or currently available coverage.

    Patent details

    The Korean grant and the related PCT application have distinct legal statuses. A PCT publication is not a worldwide patent grant. Patent records do not establish insurance authorization, government endorsement or currently available coverage.

    How the PCT process works · WIPO (opens in a new tab)
    Cryptocurrency trading-loss insurance management system
    Identifier
    10-2891022 / KR102891022B1
    Application
    10-2024-0192348
    Publication
    KR102891022B1
    Jurisdiction / procedure
    Republic of Korea
    Filed
    Grant publication

    Inventor and original assignee in the publication: 김경진 (Kim Kyung Jin). Founder profile: Walt KJ Kim.

    The documented technology addresses risk assessment, premium calculation, multi-source trigger verification, and compensation processes. Grant publication: November 24, 2025.

    Source records
    1. Korean patent publication (opens in a new tab)

      Google Patents / KIPO · Primary source

      Source published · Content reviewed

      Filing date, grant-publication date, inventor/original assignee, and documented technical architecture.

    Cryptocurrency insurance management system
    Identifier
    PCT/KR2025/021564
    Application
    PCT/KR2025/021564
    Publication
    WO2026135040A1
    Jurisdiction / procedure
    PCT international application procedure
    Filed
    Publication

    Related international application identifying Kim Kyung Jin.

    International publication WO2026135040A1. PCT is an international application procedure; national or regional offices decide patent grants.

    Reviewed November 16, 2026: the Korean patent record links the PCT application; publication metadata was corroborated by a bibliographic mirror. The primary WO publication full text could not be retrieved in this review.

    Source records
    1. PCT international-publication record (opens in a new tab)

      Google Patents / WIPO · Primary source

      Source published · Content reviewed

      Original publication link; its full text could not be retrieved during this review.

      Full source not retrieved in this review

    2. Related-application history linked from the Korean patent record (opens in a new tab)

      Google Patents / KIPO · Primary source

      Source published · Content reviewed

      The PCT application identifier, filing date, and linked international publication.

    3. International-publication bibliographic cross-check (opens in a new tab)

      Patsnap · Secondary reporting

      Content reviewed

      Bibliographic application/filing and publication identifiers/dates and applicant information.

    4. WIPO PCT guidance (opens in a new tab)

      WIPO · Primary source

      Source updated · Content reviewed

      The distinction between the PCT application procedure and national/regional patent grants.

    1. First Korean filing

    2. Korean grant publication

    3. PCT international publication

    Full chronology

    IP milestones and market events share a timeline, not a causal connection. The March 2023 USDC episode is earlier historical context.

    1. Historical context ·
      USDC/SVB reserve stress

      Historical context predating the first CryptoDam filing.

    2. Regulatory commencement ·
      Virtual Asset User Protection Act commencement

      Korea’s user-protection rules commenced before the first patent filing on 20 December 2024.

    3. IP milestone ·
      First Korean filing (opens in a new tab)

      10-2024-0192348 · Founder Kim Kyung Jin.

    4. IP milestone ·
      Korean grant publication (opens in a new tab)

      Korean granted patent 10-2891022.

    5. IP milestone ·
      Related PCT filing (opens in a new tab)

      PCT/KR2025/021564 · International application procedure.

    6. IP milestone ·
      PCT international publication (opens in a new tab)

      WO2026135040A1 · Distinct from national/regional grants.

    7. Market event ·
      Binance security incident

      Followed by funding and phased service-restoration announcements.

    Development approach

    Our interpretation of these cases guides development and pilot work. These objectives are CryptoDam’s analysis, not claims made by the cited sources or a promise to compensate any listed event.

    1. Measure the interruption.

      Develop objective event timing, evidence of affected functions and predefined duration criteria for service interruptions.

    2. Compare before interpreting.

      Use multiple price sources and venue comparisons; distinguish a persistent price deviation from an issuer’s redemption failure.

    3. Make conditions explicit.

      Link verified issuance and redemption status to eligible exposure records and explicit product conditions in pilot workflows.

    4. Keep decisions accountable.

      Connect evidence, decision ownership and review history, with appropriately funded protection arrangements where offered.

    04 / THE KOREAN CONTEXT

    Current law

    In Korea, user protection is a legal responsibility for virtual asset service providers.

    Since 19 July 2024, covered Korean virtual asset providers must prepare for specified incident liabilities.

    FSC implementation FAQ · 17 July 2024 (opens in a new tab)

    Article 8 · Supervisory rule 10

    Financial resources for incident liabilities

    Aggregate insurance or mutual-aid limits and reserves must meet the applicable minimum for specified incident liabilities.

    Amounts and scope

    Since 19 July 2024, covered virtual asset service providers in Korea—including relevant exchanges and custodians—must make financial provision for liabilities arising from specified incidents such as hacking and computer-system failures. Permitted measures include insurance, mutual aid and reserves.

    Article 8 requires covered providers to prepare for specified incident liabilities. The supervisory rule sets minimum aggregate insurance or mutual-aid limits and reserves according to customer assets and the applicable business category.

    General category

    The greater of 5% of the prescribed value of customer virtual assets outside cold storage and ₩3 billion (30억원).

    An aggregate resource requirement for the provider’s specified incident liabilities; it is not 5% plus ₩3 billion or a payout promise to each user.

    Specified no-money-exchange exception

    The greater of that same 5% amount and ₩500 million (5억원).

    Applies to qualifying providers whose customer services involve no exchange between virtual assets and money. This is an exception based on business activities, not firm size.

    Insurance or mutual-aid limits and reserves may contribute to the aggregate. Deposits or trusts at qualifying institutions are conditional fallback measures under Article 10(1), when insurance/mutual aid and reserves are both unavailable or cannot by themselves meet the amount requirement.

    The calculation totals month-end quantities outside cold storage multiplied by the prescribed preceding one-year average daily KRW conversion values at that month-end. Recalculate monthly and make required limit increases or additional funding by the 10th of the following month. Month-end and the 10th are calendar dates, not business days.

    These requirements address the provider’s specified incident liabilities. They do not establish universal coverage of market losses or stablecoin depegs. Any future retail fixed-benefit product needs a separate product and authorization assessment.

    Sources and applicable versions

    1. National Law Information Center · Virtual Asset User Protection Act, Article 8 — Insurance and other measures (opens in a new tab)
      Promulgated / published
      Effective
      Reviewed
      Reviewed version
      Act No. 21857; version effective 2 October 2026
      Articles / questions
      8
    2. National Law Information Center · Virtual Asset User Protection Act Enforcement Decree, Article 12 — Prescribed incident scope (opens in a new tab)
      Promulgated / published
      Effective
      Reviewed
      Reviewed version
      Presidential Decree No. 36728; version effective 2 October 2026
      Articles / questions
      12
    3. National Law Information Center · Virtual Asset Business Supervisory Regulation, Articles 9–10 — Valuation and incident-liability resources (opens in a new tab)
      Promulgated / published
      Effective
      Reviewed
      Reviewed version
      FSC Notice No. 2024-37; effective 19 July 2024
      Articles / questions
      9 · 10

      The standard viewer did not expose the article body. Article 10 was reviewed in the official indexed text and its amounts, calculation and deadline were cross-checked against the FSC’s 17 July 2024 explanation.

    4. National Law Information Center · FIU Reporting and Supervision Regulation, Article 27(1) — Real-name account exception (opens in a new tab)
      Promulgated / published
      Effective
      Reviewed
      Reviewed version
      FIU Notice No. 2026-3; version effective 2 October 2026
      Articles / questions
      27(1)

      The version effective 2 October 2026 was identified, but the standard viewer did not expose Article 27. The no-exchange-between-money-and-virtual-assets criterion was cross-checked against the FSC’s 22 March 2021 explanation of the finalized regulation.

      Full source not retrieved in this review

    5. Financial Services Commission · Finalized AML implementing rules — Explanation of the real-name account exception (opens in a new tab)
      Promulgated / published
      Effective
      Reviewed
      Reviewed version
      FSC explanation of finalized rules, 22 March 2021
      Articles / questions
      27(1)
    6. Financial Services Commission · FSC implementation FAQ for the Virtual Asset User Protection Act — Questions 3, 4 and 9 (opens in a new tab)
      Promulgated / published
      Reviewed
      Reviewed version
      Implementation explanation published 17 July 2024
      Articles / questions
      3 · 4 · 9

    Article 9 · Transaction records

    Records that can be traced

    Preserve prescribed transaction records for 15 years after the transaction relationship ends.

    Scope and conditions

    Article 9 requires prescribed transaction records to be retained for 15 years after the transaction relationship ends, supporting traceability and the checking and correction of errors.

    The 15-year period begins when the transaction relationship ends. An incident report alone does not establish compliance with the statutory transaction-record requirements.

    Sources and applicable versions

    1. National Law Information Center · Virtual Asset User Protection Act, Article 9 — Transaction-record preservation (opens in a new tab)
      Promulgated / published
      Effective
      Reviewed
      Reviewed version
      Act No. 21857; version effective 2 October 2026
      Articles / questions
      9

    20 August 2026 · Reporting controls

    Controls that work in practice

    Reporting review examines the adequacy and actual operation of organizational, personnel, IT and internal controls.

    Scope and conditions

    Requirements strengthened from 20 August 2026 bring the adequacy and operation of organizational, personnel, IT and internal control arrangements into the VASP reporting review.

    Apply the relevant transition provisions—including the amended reporting rules and treatment of specified pre-commencement grounds for already reported providers—when assessing an individual provider’s obligations. They are not a blanket exemption from internal-control requirements.

    Sources and applicable versions

    1. National Law Information Center · Specific Financial Information Act, Article 7(3) and relevant transitions — Reporting acceptance criteria (opens in a new tab)
      Promulgated / published
      Effective
      Reviewed
      Reviewed version
      Act No. 21857, effective 2 October 2026; retains the supplementary provisions of Act No. 21358
      Articles / questions
      7(3)

      The supplementary Articles 1, 3, 4 and 5 of Act No. 21358, promulgated 19 February 2026, were also reviewed. Transitions cover amended reporting by existing providers and treatment of specified pre-commencement grounds; they do not establish a blanket internal-control exemption.

    2. Financial Services Commission / Korea Financial Intelligence Unit · FSC/FIU revised VASP reporting-manual announcement — Reforms effective 20 August 2026 (opens in a new tab)
      Promulgated / published
      Effective
      Reviewed
      Reviewed version
      Reporting reform and manual announcement published 13 August 2026
      Articles / questions
      7(3)

      The announcement body and in-force Act were reviewed. The attached manual’s body could not be inspected, so separate final-manual issuance or application is not asserted.

    Policy and supervisory updates

    Supervisory guidance
    FSC calls for continuous response and compensation capacity

    Supervisory guidance, not a new Article 10 floor; 16 November is a follow-up to the same announcement. Status as of

    Proposed legislation

    In its 12 November 2026 announcement, the FSC said the Digital Asset Bill was still being prepared.

    Full policy record

    On 12 November 2026, the FSC called for continuous monitoring and incident response, greater cold-storage protection, and sufficient insurance compensation limits and reserves.

    Announced security measures and supervisory guidance; this release does not itself establish a new numerical Article 10 floor. The 16 November public summary follows this announcement, rather than constituting a separate enactment or incident.

    Source published
    Latest substantive update
    Status as of
    Content reviewed
    CryptoDam’s interpretation / design objective

    CryptoDam interpretation: institutions need verifiable incident response and adequate compensation resources. The guidance neither requires nor endorses CryptoDam.

    Substantive updates
    1. The FSC announced security and compensation-capacity measures and said the Digital Asset Bill was still being prepared.

    2. An FSC public summary reiterated the 12 November security measures. It is a follow-up to the same policy announcement, not a separate law or incident.

    Source records
    1. Financial Services Commission · FSC: security measures for virtual asset service providers (opens in a new tab)

      Primary source · Source published

      Supports: Monitoring and response, cold-storage protection, insurance limits and reserves, and the Digital Asset Bill then being prepared; not a newly enacted numerical supervisory floor.

      Content reviewed

    2. Financial Services Commission · FSC: protecting virtual-asset users’ assets and information — public summary (opens in a new tab)

      Primary source · Source published

      Supports: Follow-up public summary of the 12 November security measures, reiterating continuous response, cold storage, insurance limits, reserves and incident-response measures.

      Content reviewed

    Supervisory guidance
    FSC reviews reconciliation and high-risk manual controls

    A passed target date establishes neither completed implementation nor a statutory mandate for every measure. Status as of

    Full policy record

    On 6 April 2026, the FSC announced review findings and a control-improvement programme covering continuous ledger/wallet reconciliation, automated verification and multiple approvals for manual transactions, stronger internal controls and planned self-regulatory implementation.

    These are announced improvement measures and implementation plans. The announcement does not establish that every measure became a statutory mandate or was completed simply because a target date passed.

    Source published
    Latest substantive update
    Status as of
    Content reviewed
    CryptoDam’s interpretation / design objective

    CryptoDam interpretation: protection workflows need verifiable records, clear decision ownership, and review history.

    Substantive updates
    1. The FSC announced reconciliation, transaction-verification and approval-control improvements with planned self-regulatory and system implementation.

    Source records
    1. Financial Services Commission · FSC: continuous asset checks and stronger internal controls — 6 April industry meeting (opens in a new tab)

      Primary source · Source published

      Supports: Reconciliation, verification and multiple approvals for manual transactions, internal-control improvements and planned self-regulatory/system implementation; not evidence of completed implementation.

      Content reviewed

    CryptoDam’s interpretation and intended role

    Recurring incidents and Korea’s protection requirements reinforce the need for verifiable evidence and accountable compensation processes. CryptoDam is being developed to help exchanges, insurers and other institutions address that need—and help restore trust in crypto and stablecoins.

    05 / A PROPOSED PATH

    CryptoDam development planProposed launch path

    A phased path to protection in Korea

    Start with a proposed enterprise pilot; evaluate insurer-issued protection after defining coverage, lawful distribution, claims responsibilities and customer protections.

    1. Enterprise software pilot

      Defined incident evidence and sample reports, within an agreed enterprise software pilot.

    2. Insurer-led protection

      The insurer owns terms, pricing, underwriting, claims and payouts. CryptoDam supports evidence and workflow records.

    3. Expanded distribution

      Permitted distribution or scoped sandbox designation, with a separate VASP and AML assessment for stablecoin activities.

    Institutional implementation details

    CryptoDam’s proposed launch begins with enterprise incident-evidence software. An insurer-issued protection product would follow once the parties establish the coverage terms, permitted distribution arrangements, claims responsibilities and customer protections.

    01 · Enterprise software pilot

    Before starting the pilot

    Begin with defined incident detection, timestamped evidence, event reconstruction and sample reports, within an agreed enterprise pilot scope. The proposed commercial model is a fixed software or pilot fee.

    • Written scope and responsibility mapping.
    • Exchange and other data access rights.
    • Privacy and security review.
    • Signed pilot agreement.
    • Synthetic or appropriately de-identified test records.

    Assess the actual functions and contractual commitments. A fixed fee or “software” label is not a regulatory exemption.

    02 · Insurer-led protection

    Before launching the protection product

    Support an insurer-issued KRW product with evidence and workflow records. The insurer sets policy terms and pricing, underwrites the risk and retains responsibility for claims and payouts. Solicitation and regulated claims functions are performed by the insurer or other persons legally entitled to perform those functions.

    • Confirmed carrier capacity.
    • Product documentation and review.
    • Any required regulatory filings.
    • Lawful distribution.
    • Data processing terms.
    • Claims and appeals ownership.
    • Event and aggregate limits.
    • Reconciliation.
    • Tested payout authorization and release controls.

    Scope technical evidence and workflow support with the insurer. Coverage judgments, loss assessment, and insurance-money recommendations can engage regulated functions even if generated by software.

    03 · Expanded distribution

    Before activating expanded activities

    Evaluate appropriate agency or brokerage registration, or a specifically designated regulatory sandbox where relevant. Review stablecoin trading, exchange, custody, transfer and intermediary features separately before activation.

    • Obtain the applicable registrations or designation.
    • Confirm applicant eligibility and the exact permitted service, conditions, and duration.
    • Assess VASP reporting and acceptance, AML, and other applicable requirements.
    • Check the current status and transition rules of second-stage digital-asset legislation.

    Verify sandbox eligibility for the actual applicant entity. A designation provides specific permissions and relief within its stated scope.

    Regulatory sources checked: .

    Build the next protection workflow with us.

    For exchanges, insurers, financial institutions, public agencies and partners exploring investor protection in Korea and international markets.

    START WITH YOUR QUESTION

    What brings you here?

    Four services, each with a distinct job. Choose the question you’re working on to see where to start and what the process gives you.

    CryptoDam

    Know what happened. Understand the decision.

    When an exchange disruption or stablecoin incident raises questions, CryptoDam brings the sources, coverage conditions and review history into one case. Subscribers can follow their eligibility and submit proof; partner and operations teams work through the decisions behind it.

    Start with
    Incident sources, coverage rules and supporting proof
    Leave with
    A traceable eligibility and review record
    Inside CryptoDam
    CryptoDamWorkflow illustration
    01 / 03Establish the factsConceptual flow · no live account data

    The products share an approach while keeping their own responsibilities and access boundaries. A connected workflow does not imply automatic approval or movement of funds.

    ASSISTANT CONNECTIONS

    CryptoDam & Hailey, in ChatGPT and Claude.

    Find safety guides, check public-address formats, and discuss your own Hailey watchlist and alerts in the assistant you already use.

    Public directory listing pending

    ChatGPT

    Explore the core plugin, download the package, or follow the custom-connection steps available to your account. The guide explains sign-in, permissions, and current limits.

    ChatGPT connection guide
    Custom connector setup

    Claude

    Add the existing CryptoDam connector from Claude, then sign in and review your consent. Follow a public setup guide without needing access to our private app repository.

    Claude connection guide

    A place to start

    “Summarize my Hailey watchlist and alerts without changing anything.”

    You approve the requested access. Account and workspace availability apply; large watchlists and alert lists can be partial. These workflows do not trade, transfer funds, or approve payouts.

    Manage connected assistants

    THE PLATFORM GUIDE / 01—04

    What you can do here.

    Investigate an incident. Understand a market. Govern an agent. Shape your next product. See the work each platform supports and how to get started.

    01
    Incident operationsCryptodam

    Turn an incident into a clear course of action.

    Bring incident evidence, trigger checks, eligibility decisions, and payout review into one operational record. Cryptodam gives partner, operations, and compliance teams a shared place to investigate disruptions and follow each case through its next decision. Review the supporting sources, understand why a case qualifies, and keep the history available as the incident moves toward resolution.

    BUILT FOR

    Operations teams · Partners · Compliance reviewers

    Explore incident operations

    IN PRACTICE

    Evidence & verification

    Inspect source evidence and trigger checks in the context of each incident.

    Eligibility decisions

    Follow coverage conditions, affected subscribers, and the reasons behind each result.

    Payout review & history

    Work through reviewer decisions, holds, and settlement records with an audit trail.

    THE WORKFLOW

    1. 01Collect evidence
    2. 02Verify & assess
    3. 03Review settlement
    02
    Market intelligenceSilver Ocean Hailey

    Find the research behind the market move.

    Move between Korean equities, U.S. equities, and crypto without losing the research context. Silver Ocean Hailey brings asset discovery, market snapshots, published investment theses, and contributor profiles into one workspace. Start with a symbol, examine the available data and source freshness, then follow the ideas and people that matter to your own research process.

    BUILT FOR

    Market researchers · Individual investors · Contributors

    Explore Silver Ocean Hailey

    IN PRACTICE

    Three markets, one workspace

    Browse Korean and U.S. stocks alongside crypto, with asset detail and available pricing.

    Published research

    Read a contributor’s thesis, stance, and symbol context before forming your own view.

    Watchlists & community

    Organize symbols, discover contributor profiles, and explore research rooms.

    THE WORKFLOW

    1. 01Discover an asset
    2. 02Read the research
    3. 03Build your watchlist
    03
    Agent governanceAgentGuard

    Give agents a mandate. Keep decisions accountable.

    Define what an agent is allowed to do before an action reaches your systems. AgentGuard connects agent identities, mandates, policy evaluation, human review, and action receipts. Teams can examine the requested action against its limits, escalate decisions that need approval, and trace the resulting evidence back to the agent and policy involved in the decision.

    BUILT FOR

    AI product teams · Platform operators · Risk reviewers

    Explore agent governance

    IN PRACTICE

    Mandates & limits

    Set permitted assets, purposes, spending limits, expiry, and approval thresholds.

    Policy & human review

    Evaluate proposed actions and route decisions through the applicable approval process.

    Receipts & audit history

    Connect the authorization, action receipt, and incident history for later review.

    THE WORKFLOW

    1. 01Define the mandate
    2. 02Evaluate the action
    3. 03Review the receipt
    04
    AI product labGenesis

    Build with a process that learns from the result.

    Keep product context, research, implementation plans, and measured outcomes connected across development cycles. Genesis helps founders and product teams turn a question into a guided mission, develop an idea into a build packet, and bring the implementation result back for review. Human approval shapes the next step, while recorded lessons help inform the work that follows.

    BUILT FOR

    Founders · Product teams · Venture studios

    Explore the Genesis lab

    IN PRACTICE

    Context & research missions

    Capture the product brief, investigate opportunities, and organize research findings.

    Implementation packets

    Turn an approved idea into structured prompts, implementation phases, and test checklists.

    Experiments & learning

    Record implementation outcomes, compare experiments, and decide what to iterate next.

    THE WORKFLOW

    1. 01Research the question
    2. 02Prepare the build
    3. 03Evaluate & learn
    An illustrated coastal observatory with research folios on a circular table
    STUPORE / A conceptual space for research and considered decisions

    THE WAY WE BUILD

    Complex work deserves a clearer process.

    Stupore builds tools for people investigating uncertain information, reviewing choices and preparing their next move. Our four products bring that approach to different kinds of work.

    1. 01

      Keep the evidence close.

      A result is more useful with its available sources, timing and context. We design the work around understanding the reasons behind it.

    2. 02

      Keep decisions accountable.

      Research, policy evaluation and approval have different roles. Consequential decisions stay with the people authorized to make them.

    3. 03

      Make the next step legible.

      A reviewed case or an approved brief should help the next person act with context. The record stays connected to the work.

    Meet Stupore and the products

    BEFORE YOU BEGIN

    A few useful answers.

    Understand where to start, what to expect, and how to access the right workspace.

    Talk to the team
    Which platform should I start with?

    Choose Cryptodam for incident operations, Silver Ocean Hailey for market research, AgentGuard for oversight of financial AI agents, or Genesis for supervised product development. Each has its own workspace and purpose.

    Can I explore without an account?

    The product overviews are public. The Hailey workspace requires sign-in. AgentGuard requires an authorized workspace role, and Genesis access is reviewed. You can explore each overview before requesting access.

    Which markets does Hailey cover?

    Korean stocks, U.S. equities, and crypto. Symbol pages, market snapshots, analyst theses, and watchlists give different views of an asset. Coverage and available observations vary by asset and data provider.

    How can I tell whether market data is current?

    On Hailey symbol pages, check the source, observation time, and available freshness label. A market snapshot can be older than a live quote, and availability varies by provider.

    Does Genesis deploy products on its own?

    Genesis organizes research, scored ideas, build packets, implementation outcomes, and experiments. Teams review what to build and learn from the result. Deployment and other consequential actions remain supervised.

    How do the four products fit together?

    Each product has its own workspace, workflow, and access rules. They support complementary jobs: researching markets, handling incidents, supervising agents, and developing products. Choose the workflow you need from the product guide.

    Take a closer look

    Explore the visual product map or inspect sourced market data.

    CRYPTODAM / STUPORE

    Your next move.

    Explore the workspace, or talk with us about your team’s workflow.

    Checking account…Contact the team