Skip to content
Merulan

Ramp setup

What an operator supplies to connect the Ramp Source, and the verification the provider requires.

Connecting Ramp redirects the operator to the provider and returns with a grant. Merulan holds the credential directly. An operator who holds the material below connects in one pass.

Prerequisites

Ramp refuses the connection until every item holds.

  • A Ramp account, and an administrator who may approve a connected application.
  • Card or bill transactions in Ramp for the periods a Pipeline reads.

Credentials

Ramp stores the credential under the direct custody the registry declares, so Merulan never shows the secret again once the connection is saved.

  • No secret is typed into Merulan. The browser grant returns an access token and a refresh token, and Merulan seals both.

Scopes

Ramp requests the scopes the registry declares, and a grant missing one of them fails the first collection read.

  • transactions:read

Merulan compares the granted scopes with the asked-for scopes in both directions, so a grant carrying a wider scope is refused rather than stored.

Verification

Provider app review governs the Ramp connection. Ramp reviews the registered application before it may connect a production account.

  • Connect and map a Source runs the connect ceremony and binds collections once the credential is in hand.
  • Integrations lists every Source that carries a setup page, with its ceremony and verification posture.