Wever Labs

Agent payment reference completion

Agents that already have payment authority can complete a rail run without a human checkout screen. Supply a payment reference, run the rail, receive the return package, verify the receipt, and store proof.

Read self-serve contract Agent self-serve loop

Machine path

  1. POST quote_paid_rail_run.
  2. Attach payment_reference, wallet_reference, invoice_reference, stablecoin_reference, x402_reference, or ap2_mandate_reference.
  3. POST complete_payment_reference_run or complete_paid_rail_run.
  4. Receive production_run, return_package, receipt, verification_packet, receipt_ledger_entry, and transcript_hash.

Example

curl -X POST https://weverlabs.com/api/agent-self-serve-rail-loop   -H "Content-Type: application/json"   -d '{
    "mode": "complete_payment_reference_run",
    "rail_key": "packetops",
    "movement_type": "transaction",
    "movement_amount_units": 1000,
    "payment_reference": "agent_reference:example_paid_authority",
    "idempotency_key": "agent-payment-reference-run-001",
    "packet_type": "agent_supplied_packet",
    "available_documents": ["intake_form", "identity_attestation", "packet_summary"],
    "expected_documents": ["intake_form", "identity_attestation", "packet_summary", "authorization_form"]
  }'

Boundary

This path does not create custody or unsupported autonomous money movement. It accepts a supplied payment authority or payment reference and returns durable proof. Stripe Checkout remains available when a payer needs a hosted payment screen.

Payment methods

All rails accept agent payment authority.

Agents can use hosted checkout, agent allowance references, wallet references, invoice references, stablecoin references, x402 references, or AP2 mandate references across PacketOps, DiligenceOps, EnergyOps, DistributionOps, TokenOps, FinanceOps, ContractOps, and Scout.