MCP
A2APrerequisites
Before continuing, you should have already completed the following for this connector:Configure the Connector
Connector Profile
Link an Account
Link Account
Webhook subscription (managed by StackOne)
You do not need to set up anything in the Ramp dashboard to receive webhook events. When you connect your Ramp account, StackOne automatically registers a webhook subscription with Ramp, completes Ramp’s verification handshake, and starts receiving events. When you disconnect the account, StackOne removes the subscription again — the entire lifecycle is handled for you.
Grant the right permissions to receive events
Ramp only sends events for the resources your connection is allowed to read. To receive a resource’s events, your connection needs that resource’s read scope — for example, transaction events require transactions:read, bill events require bills:read, and unified request events require unified_requests:read. By default the connector requests all of its scopes, so every event type is covered. If you enter a smaller set of scopes in the optional Scopes field when connecting, events for the resources you left out will not be delivered.
- Also enable the same scopes on your Ramp developer app (under Scopes in the app settings) — Ramp will refuse the connection if it asks for a scope the app does not allow.
- Two exceptions need no scope at all:
payments.updated(Ramp has no public scope for it) andtests.test_event(used only for delivery testing).