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.
Installs into .claude/skills of the current project.
Are you the author of Plaid Fintech?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/omer-metin-plaid-fintech)
---
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.
