Building a Travel Rule Auto Configer with Google AI and Vibe Coding

Published: July 1, 2026
Category: AI / RegTech
Reading Time: 6 minutes

---

We entered the GDG Google AI Vibe-a-thon with a proposal rooted in a very real operational pain point: Travel Rule compliance across multiple jurisdictions.

Here's what we're building and why.

---

The Problem

Travel Rule compliance requires VASPs to transmit customer identification information to counterparty VASPs for transactions above certain thresholds. The complexity comes from the fact that every jurisdiction defines "threshold" and "required information" differently:

| Jurisdiction | Regulator | Threshold | Key Features | |---|---|---|---| | Hong Kong | HKMA | HKD 8,000 | Specific data fields mandated | | Singapore | MAS | SGD 1,500 | Different field requirements | | EU | MiCA | EUR 1,000 | GDPR privacy constraints layered | | United States | FinCEN | USD 3,000 | Distinct formatting standards | | Japan | JFSA | Variable | Separate thresholds and structures |

The current workflow for a VASP processing cross-border transactions:

1. Compliance analyst receives transaction
2. Manual research to determine applicable jurisdiction's rules
3. Manual field mapping using spreadsheets
4. Manual construction of compliant data transmission
5. Manual verification before sending

For a mid-tier exchange processing thousands of transactions monthly, this is a significant operational burden. For smaller VASPs without dedicated compliance engineering teams, it is often done poorly — or not at all.

---

Our Solution: Travel Rule Auto Configer

We're building an AI Agent powered by Google's Gemini API that automates this workflow end-to-end.

Architecture

Regulatory Texts (HKMA, MAS, MiCA, FinCEN...)
         ↓
    Gemini API — Knowledge Base Processing
         ↓
Transaction Parameters (jurisdictions, amount, asset)
         ↓
    Gemini API — Rule Identification + Configuration
         ↓
    Output: IVMS101 JSON + Config File (30 seconds)

Step-by-Step Flow

1. Knowledge base construction — Regulatory guidance documents are ingested into Gemini's context, structured by jurisdiction, threshold, data field requirements, and transmission format specifications.

2. Transaction input — User enters: sender jurisdiction, receiver jurisdiction, transaction amount, and asset type.

3. Rule identification — The AI Agent cross-references transaction parameters against the knowledge base, identifies which regulations apply, and determines whether the transaction exceeds the relevant thresholds.

4. Configuration generation — The Agent outputs a complete compliance configuration including: required data fields, IVMS101-compliant JSON structure, counterparty endpoint (if known), and regulatory notes (data sharing agreement requirements, privacy disclaimers, etc.).

5. Export — A ready-to-use configuration file, directly importable into the VASP's existing compliance system.

Complete cycle: approximately 30 seconds from input to export.

---

The Vibe Coding Process

Here is the part that surprised even us.

We are a compliance technology provider — not a software company. We do not have a dedicated engineering team.

Vibe Coding changes the equation completely.

We began in Google AI Studio, prototyping the prompt structure and testing different knowledge base architectures. We validated that regulatory text could be effectively chunked, indexed, and retrieved within Gemini's context window.

Then we described the tool in natural language to a generative coding assistant:

"Build a web interface for a Travel Rule compliance configurator. Input fields: sender country, receiver country, amount, asset type. Output: applicable regulations, required data fields, IVMS101 JSON format, endpoint address. Clean compliance-industry aesthetic."

Code was generated. We tested. Errors appeared. We copied error messages back to the AI. The AI fixed them. We tested again. Approximately 8 iterations later, a working prototype emerged.

Zero lines of code written by a human.

---

The GDG Vibe-a-thon Context

We are submitting on the "Truth" track — addressing a real operational pain point with Google AI.

The judging criteria are:

| Criterion | Weight | Our Alignment | |---|---|---| | Completion & propagation | 25% | Working prototype, not a mockup | | Deep Google AI usage | 25% | Gemini API at core of knowledge base and rule identification | | Innovation & Vibe Coding expression | 20% | Zero hand-written code; natural language → prototype | | Social value & feasibility | 20% | Lowering compliance barriers for small VASPs globally | | Cross-cultural empathy | 10% | Understanding regulatory differences across jurisdictions |

---

Beyond Travel Rule

The same architectural pattern — regulatory knowledge base + Gemini API + vibe coding — applies across multiple compliance use cases:

• Sanctions screening configuration — automatically determine which sanctions regimes apply to a given transaction based on jurisdiction, entity type, and counterparty location
• KYC document auto-review — identify which documents are required based on jurisdiction, entity type, and risk profile
• SAR auto-generation — draft Suspicious Activity Reports based on transaction patterns and applicable regulatory formats
• Regulatory reporting — auto-generate filings in each jurisdiction's prescribed format

Each follows the same architecture: regulatory text → AI knowledge base → transaction parameters → AI analysis → compliant output.

---

Conclusion

Travel Rule compliance across multiple jurisdictions is a significant operational burden for VASPs of all sizes. The combination of Google's Gemini API for regulatory knowledge base construction and Vibe Coding for rapid prototyping makes it possible to build practical compliance tools without a dedicated engineering team.

Our prototype is running. The submission is in progress. The GDG Vibe-a-thon deadline is July 15, with Top 30 entries invited to submit demo videos, and Top 6 presenting at Google I/O Connect in Shanghai on August 12.

If you are working on Travel Rule compliance, AML automation, or using Google AI for regulatory technology — reach out. We are building this in the open.

---

Links: GDG Vibe-a-thon Official Page · UWAY Travel Rule Readiness
Tags: #GDG #Vibeathon #GoogleAI #GeminiAPI #TravelRule #Compliance #RegTech #VibeCoding #AI #VASP #UWAY #AML