Skip to content

Ramp

PropertyValue
AlgorithmHMAC-SHA256 (hex-encoded, with Base64 fallback)
HeaderX-Ramp-Webhook-Signature

Signing formula:

hex(HMAC-SHA256(raw_payload, secret))

Transyt first attempts hex-encoded verification. If that fails, it falls back to Base64-encoded comparison for compatibility.

Ramp sends a verification challenge when you first register a webhook endpoint. Transyt automatically handles this by detecting webhooks.verification events and responding with the challenge string.

  1. In the Ramp Developer Dashboard, configure your webhook endpoint:
    https://ingest.transyt.com/ramp/{your-account-slug}
  2. Ramp will send a verification challenge, which Transyt handles automatically
  3. Copy the webhook signing secret from Ramp
Terminal window
curl -X POST https://ingest.transyt.com/admin/accounts \
-H "X-Admin-Token: YOUR_ADMIN_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"provider": "ramp",
"account_slug": "main",
"app_key": "my-app",
"signing_secret_current": "your-ramp-webhook-secret"
}'

Ramp has 40+ event types. Here are the most common:

Ramp EventTransyt Event
transactions.authorizedtransaction.authorized
transactions.clearedtransaction.cleared
Ramp EventTransyt Event
cards.createdcard.created
cards.suspendedcard.suspended
Ramp EventTransyt Event
USER_CREATEDuser.created
Ramp EventTransyt Event
webhooks.verificationverification

Transyt looks for id, event_id, or webhook_id fields in the payload. For verification challenge events, the external ID is challenge_{challenge_string}.