Skip to main content
Cross-Rail Authority

Let agents transact without giving them the keys

Payment partners move the money. On a completely mediated covered path, EMILIA Gate checks whether the exact transaction has accepted authority and required evidence before provider entry. Human approval is one optional evidence source when the buyer's policy requires it.

$25K · 90 days · 1 protected workflow. Synthetic and read-only validation first; production only through a buyer-approved Gate boundary.

Scope the protected-workflow pilotRead the Protocol

One authority contract across configured payment partners

Exact transaction admission
Bind amount, currency, counterparty, instrument, operation, and partner request before the rail is entered.
Human interruption when needed
Let an external policy or risk service select when standing authority is insufficient, then bind the human decision to the same action.
Single-use rail entry
Mint one opaque, short-lived permit only after current authority and an atomic budget reservation have passed.
Uncertain outcomes stay uncertain
A lost provider response is fenced for authenticated reconciliation—not converted into a blind retry.

What Gate evaluates and records before a transaction reaches a partner

  • Who or what is acting, under which bounded authority
  • The exact amount, currency, counterparty, instrument, operation, and provider request
  • Which current policy and allowance permitted the action
  • Why a human was—or was not—interrupted
  • A separately verified, action-bound human decision when required
  • An atomic budget reservation and one-use connector permit
  • A durable distinction between executed, refused, and indeterminate

Authority, not custody

EMILIA is not a bank, escrow service, custodian, or settlement rail. Native payment partners remain authoritative for authentication, mandates, funds, KYC/AML, settlement, refunds, and disputes. Gate controls only whether one exact action may enter a configured connector.

See EMILIA Gate →See Emilia Eye →

Best first pilot

Map and validate one customer-owned Gate around one typed partner action. The public pilot remains synthetic and read-only; production is separately scoped after buyer acceptance.

  • Define one bounded operating allowance
  • Pin one external policy or risk decision source
  • Require human interruption above an agreed threshold
  • Measure refused, admitted, and indeterminate transactions without exposing payment details