Skip to main content
Version: 2.0

Integration Phases: Your Path to a Successful Integration

This guide outlines the key phases of integrating Fraudio's services into your system for a seamless onboarding experience.

🚀 Kickoff​

Key Activities:

  • Kickoff Call: Fraudio conducts an initial kickoff call to discuss expectations and clarify the integration process.
  • Setup Communication Channels: Fraudio sets up a communication channel for ongoing support.
  • Integration Info Pack: Fraudio shares an integration info pack.
  • Portal Access: The assigned admin receives access to the portal, enabling user invitations and role assignments, as well as the ability to create API keys.

✅ Requirements to Proceed: Integration requirements are clearly understood, and portal access is configured and functional.

🛠 Technical Integration Phase​

Risk Scoring Status: Risk recommendations received via the API response should be ignored during this phase, as the transaction data is not yet reliable.

Key Activities: During this phase, the client begins sending data and aligning their systems with Fraudio's. The process includes the following steps:

  1. Follow the Quickstart Guide:
    Use the Quick Start Guide to create test API keys and send your first API call.

  2. Map Your Data to Fraudio's Schema:
    Map your internal fields to match Fraudio's expected format. For detailed guidance, refer to the Mapping Guide.

    To accelerate your path to Live Mode, we recommend focusing on the most critical integration elements first:

    • Required fields: For more information on the required fields, please refer to the Fraudio Data Schema.
    • Critical transaction events: Integrate the core payment transaction flow first.
      • Score critical events (typically the authorization request, MTI 0100) via Financial Events Screening.
      • For pre-authorization integrations, send the matching authorization response (MTI 0110) and other non-scored follow-up transaction events (captures, reversals, refunds, and similar) via Financial Events Enrichment where needed.
      • For post-authorization-only integrations, score the authorization response (or equivalent) on Screening with full transaction context.

  3. Data Quality Review:
    Fraudio will assess the completeness, accuracy, and consistency of the submitted data to ensure it meets the minimum requirements for production use.

  4. Transition to Live Mode:
    Once data quality is approved, you can switch to production mode using your live API keys.

✅ Requirements to Proceed: Critical pre- and post-authorization transaction events are flowing correctly (with enrichment where needed), critical and required fields are included in the payloads, and data quality is approved by Fraudio.

⚫ Go Live - Warm Up Phase​

Risk Scoring Status: Risk recommendations are now available but will only be triggered by rules that are enabled in the portal.

Key Activities:

  • Products Deep Dive: The risk team is now actively involved in this phase. They will participate in product-focused information sessions to review settings and align on next steps.

  • Enable Initial Rules: Enable initial rules to start scoring and monitoring transactions. Any additional fields that are not yet available can be added by expanding on the integration or contacting the Fraudio team.

  • Share Additional Data: Extend the integration beyond the critical transaction flow. As with the technical integration phase, we recommend starting with test API keys, then live keys once the data is reviewed and approved by Fraudio.

    • Optional fields: For more information on optional fields, please refer to the Fraudio Data Schema.
    • Lower-priority events and entity updates: Send additional event types and entity context via Financial Events Enrichment, for example:
      • Dispute events (chargebacks, TC40/SAFE, and related lifecycle updates)
      • Entity updates (merchants, cards, wallets, and other relevant entities) using an entities-only payload
      • Other enrichment event types relevant to your product setup

  • Accumulate Transaction Data: The accumulation of transaction data is needed for model and rule validation. The accumulation can be accelerated by doing a batch transfer of historical data. For more details on the batch transfer process, refer to the Batch Transfer Guide.

✅ Requirements to Proceed: Products are enabled with initial conservative scores and predictions.

🎛 Tuning Phase​

Risk Scoring Status: Risk recommendations continue to be triggered by the rules enabled in the portal. Additionally, Fraudio's models are conservatively configured but will now begin adapting to your data and risk preferences through tuning.

Key Activities:

  • Enable Additional Rules: Finalize the rule setup by enabling any remaining rules relevant to your risk strategy.
  • Model Tuning: An iterative phase where Fraudio collaborates with you to refine model behavior.
    • Model Training: Fraudio applies the agreed-upon tuning settings to retrain and adapt the models.
    • Performance Review: Both teams review model outcomes, thresholds, and scoring behavior to ensure alignment with expectations.

✅ Requirements to Proceed: Tuning settings have been finalized, applied to the models, and validated through a joint performance review.

🏁 Supported Mode​

Risk Scoring Status: Rules and models are fully operational and adapted to client data.

Key Activities:

  • Monitoring & Optimization: Continuously monitor scoring performance, rule effectiveness, and operational KPIs. Adjust configurations as needed.

  • Active Feedback Loop: Maintain an open feedback loop using the portal or support channels to share observations and insights that can inform future improvements.

  • Optional Enhancements: Enable additional endpoints, send new data fields, or activate new products as your use case evolves.

  • Scheduled Reviews (Optional): Set up periodic check-ins with the Fraudio team to review system performance, align on product updates, and identify opportunities for optimization.