Skip to content

Update signal_guide.md #28

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
noitsnotit merged 1 commit into from
Oct 13, 2025
Merged

Update signal_guide.md #28

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions rules/signal_guide.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,13 +1,13 @@
# Plaid Signal Integration (Sandbox End-to-End Guide)
# Plaid Signal Transaction Scores Integration (Sandbox End-to-End Guide)

## Overview

This guide provides a complete, step-by-step integration of Plaid's **Signal** product using the **Sandbox** environment. It is intended to support both **frontend** and **backend** implementations in a language-agnostic format with optional language-specific hints. The goal is to enable an AI agent or developer to execute a fully functional Plaid Signal integration, from user bank linking to evaluating ACH payment risk.
This guide provides a complete, step-by-step integration of Plaid's **Signal Transaction Scores** product using the **Sandbox** environment. It is intended to support both **frontend** and **backend** implementations in a language-agnostic format with optional language-specific hints. The goal is to enable an AI agent or developer to execute a fully functional integration, from user bank linking to evaluating ACH payment risk.

Assumptions:
- The developer has a Plaid account and Sandbox `client_id` and `secret` are available. If not provided, please ask the users for it.
- The application is able to make HTTP requests.
- You have been approved for Signal access (or are using Sandbox while waiting for approval).
- You have been approved for Signal Transaction Scores access (or are using Sandbox while waiting for approval).

This document references Plaid's official documentation using markdown links.

Expand All @@ -22,7 +22,7 @@ Before starting the integration, ensure the following:
- You have obtained your **client ID** and **Sandbox secret** from the dashboard.
- You are working in the [Sandbox environment](https:/plaid.com/docs/sandbox/overview) where test credentials and institutions are available.
- Your development environment can serve both **frontend** and **backend** logic. The backend must be able to securely manage sensitive credentials and handle API calls.
- You have applied for and received approval for Signal (or have received Sandbox access while waiting for approval).
- You have applied for and received approval for Signal Transaction Scores (or have received Sandbox access while waiting for approval).

## Step 1: Create a Signal Ruleset in the Dashboard

Expand Down Expand Up @@ -152,9 +152,9 @@ After the user completes the Link flow, your frontend receives a `public_token`.

> Store `access_token` securely on your backend. Never expose it to the frontend.

## Step 5: Backend - Evaluate Transaction Risk with Signal
## Step 5: Backend - Evaluate Transaction Risk

Now that you have an access token and account ID, you can evaluate the risk of an ACH transaction using Signal.
Now that you have an access token and account ID, you can evaluate the risk of an ACH transaction.

### 5.1 API Endpoint

Expand Down