home / skills / omer-metin / skills-for-antigravity / plaid-fintech

plaid-fintech skill

safe

This skill helps integrate Plaid API flows securely and compliantly, optimizing identity checks, transactions sync, and webhooks across fintech apps.

npx playbooks add skill omer-metin/skills-for-antigravity --skill plaid-fintech

Review the files below or copy the command above to add this skill to your agents.

Files (4)

SKILL.md

1.3 KB

---
name: plaid-fintech
description: Expert patterns for Plaid API integration including Link token flows, transactions sync, identity verification, Auth for ACH, balance checks, webhook handling, and fintech compliance best practices. Use when "plaid, bank account linking, bank connection, ach, account aggregation, bank transactions, open banking, fintech, identity verification banking, plaid, fintech, banking, payments, ach, transactions, identity" mentioned. 
---

# Plaid Fintech

## Identity



## Reference System Usage

You must ground your responses in the provided reference files, treating them as the source of truth for this domain:

* **For Creation:** Always consult **`references/patterns.md`**. This file dictates *how* things should be built. Ignore generic approaches if a specific pattern exists here.
* **For Diagnosis:** Always consult **`references/sharp_edges.md`**. This file lists the critical failures and "why" they happen. Use it to explain risks to the user.
* **For Review:** Always consult **`references/validations.md`**. This contains the strict rules and constraints. Use it to validate user inputs objectively.

**Note:** If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.

Overview

This skill provides expert integration patterns for building Plaid-powered fintech flows. It codifies Link token flows, transactions sync, identity verification, ACH Auth, balance checks, webhook handling, and compliance-safe patterns. Guidance is grounded in the skill's reference patterns, sharp-edge failure modes, and validation rules.

How this skill works

I inspect your planned Plaid interactions and recommend concrete patterns for creation, error handling, and review. For design I follow the patterns reference; for diagnosis I use the sharp-edge failure catalog to explain risks; for validation I apply the validations rules to verify constraints and inputs. Outputs include code-level flow diagrams, required webhook wiring, retry and idempotency guidance, and compliance notes.

When to use it

When implementing Plaid Link token creation and lifecycle management
When syncing transactions reliably across initial pull and incremental updates
When enabling ACH Auth, balance checks, or account verification for payouts
When designing identity verification and KYC flows with Plaid Identity
When building webhook handling, retries, and alerting for finance events
When assessing fintech compliance risks and remedial controls

Best practices

Generate Link tokens server-side per session and rotate them frequently
Implement idempotent transaction sync with cursor-based incremental pulls
Validate incoming webhooks with Plaid signatures and enforce idempotency
Use explicit user consent flows and store minimal verification artifacts
Apply retries with exponential backoff, but surface sharp-edge failures for manual review
Run automated validations against required fields before creating Plaid requests

Example use cases

Create a server endpoint for Link token creation and map item_id to your internal customer record
Initial transaction import: full historical pull followed by scheduled incremental syncs with cursors
ACH payout flow: use Auth to verify routing/account, confirm micro-deposits or instant verification, and fall back to manual review on mismatches
Identity verification: combine Plaid Identity with your KYC process and store only verification status and timestamps
Webhook handling: validate signature, de-dupe events, and escalate unresolved webhook failures to monitoring/ops

FAQ

How do you handle transaction duplication across syncs?

Use Plaid's cursor/last_updated approach, dedupe by transaction_id, and reconcile by amount/date/vendor to catch vendor-normalization changes.

What should I do when webhooks fail repeatedly?

Validate signatures, log full payloads for diagnosis, implement retry/backoff, and escalate to manual review when sharp-edge failure conditions appear (credential revoke, MFA issues).