Ramp

Overview

Ramp is a corporate card and spend-management provider. In Preczn, Ramp is an Issuing connection. Boarding a merchant creates a Ramp finance application and tracks its approval lifecycle.

Ramp's onboarding differs from most Preczn connections in one important way: Ramp hosts its own application form and terms. Preczn collects the merchant's data first, then creates and prepopulates the Ramp application with it — the merchant finishes the application inside Ramp's own flow. Because Preczn reuses data it already holds for the merchant (from onboarding to another connection, or from a multi-connection form), much of the Ramp application is filled in for them, so there's less to re-enter. Boarding takes three steps:

1. Configure the connection — add your Ramp API credentials once, at the platform level.
2. Configure the boarding form — enable the Ramp fields, including the required primary contact.
3. Board the merchant — Preczn creates the application, the merchant completes it in Ramp's hosted flow, and status is tracked by webhook.

For general boarding, see Boarding Forms and Multi-Connection Boarding Forms.

Configuring the Connection

Go to Connections → Add Connection and select Ramp. Both fields are required.

ℹ️ Where do these come from?

Both values come from your Ramp developer application (Ramp Developer Console). If you don't have them, reach out to your Ramp contact.

Click Verify Connection to confirm the credentials, then save. Verification checks that Preczn can authenticate with Ramp using the credentials — it does not require an existing merchant.

Configuring Boarding Forms

When you build a form that includes a Ramp connection, note the following.

Primary contact

Ramp requires a Primary Contact (the applicant) — the person who will represent the business in the Ramp application. On the form, designate an existing owner, an existing contact, or add a new contact. This contact must include a title.

Owner and business information

Ramp requires standard business and ownership details. Two things to be aware of:

• Full SSN is required for owners. Ramp itself only needs the last four digits, but Preczn collects the full SSN and derives the last four to send to Ramp. This keeps the full SSN on file for future boarding to other connections, which more often require it to underwrite.
• Owners with 25% or more ownership are treated as beneficial owners, so make sure all owners at or above that threshold are included.

Terms & Conditions and banking

Because Ramp hosts its own application flow, two things behave differently on a Ramp form:

• Terms & Conditions — Ramp presents its own terms inside its hosted application, so Preczn does not show a Terms & Conditions step for Ramp, even when T&Cs is enabled on the form.
• Banking details — collected on the form for Preczn's records, but not sent to Ramp. Ramp collects the merchant's banking details in its own hosted flow, after approval.

Boarding a Merchant

When the merchant submits the boarding form, Preczn creates the finance application with Ramp and Ramp returns an application ID immediately. Ramp then emails the merchant to finish the application in its hosted flow; when they're done, the merchant is automatically returned to Preczn and Ramp begins its review.

sequenceDiagram
    participant M as Merchant
    participant V as Vertical SaaS Platform
    participant P as Preczn
    participant R as Ramp

    M->>P: Submit boarding form
    P->>R: Create finance application
    R-->>P: Application ID returned
    P->>P: Store application ID,<br/>set status = Sent
    P-->>V: Merchant status webhook (Sent)

    R-->>M: Email link to Ramp's hosted application
    M->>R: Complete application & consent
    R-->>P: Merchant automatically returned to Preczn
    P->>P: Update the merchant's status from Ramp

    loop On each Ramp status change
        R-->>P: Application status webhook
        P->>P: Fetch latest status from Ramp,<br/>map to Preczn status
        P-->>V: Merchant status webhook
    end

ℹ️ "Sent" does not mean done

Ramp returns the application ID as soon as Preczn creates the application, so the merchant lands in Sent right away. Sent only means the application exists — the merchant still has to complete Ramp's hosted application before Ramp starts reviewing and the status moves to Underwriting.

Merchant Status Mapping

Preczn tracks Ramp application status by webhook and maps each Ramp status to a Preczn connection status:

ℹ️ Unrecognized statuses

If Preczn receives a status it doesn't recognize (or no status), it defaults the merchant to Sent.

Testing in the Sandbox

In TEST mode you can simulate Ramp's approval decision without waiting on Ramp.

First, get the test merchant to Underwriting: board the merchant and have them complete Ramp's hosted application in the sandbox so Ramp puts it into review.

Then, in the Dashboard, open the merchant's detail view and click the Ramp connection chip in the Connections section to open its connection drawer. (You can also open the same drawer from the Vault by clicking the merchant's Ramp connection.) In the drawer you'll find two buttons: Simulate APPROVED and Simulate REJECTED. Clicking one asks you to confirm, then submits that decision to Ramp's sandbox.

These buttons:

• Appear only on a Ramp connection that is in Underwriting, while the dashboard is in TEST mode and the merchant is a test merchant.
• Trigger the decision in Ramp's sandbox, which then sends the real status webhook back to Preczn — so the merchant transitions the same way it would in production.

FAQ