Enruta

Docs · preview

Rails

Enruta connects to the accounts you already have with credentials your administrator scopes on the rail’s side. It never holds the funds and never sees a card number.

Stripe Issuing

  1. Your administrator creates a restricted key on your Stripe account with Issuing write and webhook read, and enters it in the console.
  2. On allow, Enruta creates a single-use virtual card: amount equal to the mandate, the payee as the allowed merchant, expiry equal to the mandate’s.
  3. Stripe sends issuing_authorization.request to Enruta; Enruta answers inside the two-second window by checking the authorization against the mandate and the card controls. The answer is recorded with the time it took.
  4. The posted transaction is matched back to the mandate and the record’s outcome is filled.

The card token or the network token is what reaches the payee; the card number is never returned to the agent and never stored by Enruta.

Ramp

A spend limit is created for the mandate’s amount and purpose; the virtual card is issued against it with the merchant and category restrictions the policy allows. Enruta matches the posted transaction after it lands.

Mercury

A virtual card is issued with a spend limit equal to the mandate, on a cardholder your administrator created in Mercury. Enruta reads transactions to fill the outcome.

Bill.com

For invoices, the mandate becomes an approval scoped to one bill, from an approver identity your administrator assigned to Enruta. Enruta reads with an auditor-role user and writes only the approval.

Protocol checkouts

For UCP and AP2 checkouts, Enruta supplies the ap2.checkout_mandate proof the merchant requires and keeps the merchant’s consent object by digest. For x402 and MPP, receipts are captured into the record; the payment itself runs on the customer’s own wallet or account.

Adding a rail

Each rail is a thin adapter with three duties: compile a mandate into the rail’s control, answer or observe the rail’s authorization, and match the posting back to the record. Adapters are the only rail-specific code; the policy engine and the record never change.

← CLISecurity →