Stripe (stripe pay / Treasury outbound payments) — transfer_postedAction contract

The agent may send a transfer only within the per-transfer limit, in an allowed currency, and within the agent's 24-hour total. The action's subject is the intended recipient (Stripe's recipient id, `acct_…`, or the profile the agent was told to pay, linked to it). A successful transfer must show up in Stripe as an OutboundPayment to that recipient created within the window and reaching `posted` (funds left the account); its amount must equal the amount requested. A second transfer to the same recipient within the window, a transfer that failed to confirm, or one that was returned by the receiving side within 30 days, fails the action.

Contract ID: stripe_b2b_transfer
Source: https://docs.stripe.com/api/v2/money-management/outbound-payments/object
Retrieved: 2026-10-28
Notes: Status values and their meaning are quoted from the reference: `processing` (created, funds held by a pending transaction), `posted` (confirmed, funds have left the account), `failed` (failed to confirm, funds returned by voiding the pending transaction), `canceled` (canceled before posting), `returned` (failed to arrive at the destination; funds return with a second posted transaction). The Treasury v1 object (https://docs.stripe.com/api/treasury/outbound_payments/object) carries the same five statuses and is read the same way. The `stripe pay` reference (https://docs.stripe.com/cli/pay, retrieved the same day) states that the command can move money, that `--yes` is to be added only after the user confirms recipient, amount, currency and source financial account, and that the recipient must never be guessed. Limits below are template values.

What the contract checks

Each block is evaluated against read-only facts from the systems of record. The agent's own report is never used as evidence.

Unknown fields

Things the source has not published. No value is assumed for these.

stripe_pay_object_type

Contract YAML

The machine-readable action contract: allowed action, required inputs, preconditions, limits, expected and forbidden effects, window. Sign in to select it for your tenant or fork it.

# Stripe business-to-business transfer — action contract for an agent that pays a business from a Stripe
# financial account (`stripe pay`, or the Treasury MCP tool `send_money`). Stripe's own safeguards run before the
# money moves: a directory lookup, a dry run, a person's approval. This contract runs after: it reads Stripe's
# record of the OutboundPayment and says whether the transfer the agent reported exists, went to the intended
# recipient, once, for the amount asked, reached `posted` (funds left the account), and was not returned.
# The status meanings are Stripe's, transcribed from the OutboundPayment reference (source_citation); the limits
# are template values to replace with your own.
id: stripe_b2b_transfer
version: 1
kind: action
vendor: stripe
vendor_display: "Stripe (stripe pay / Treasury outbound payments)"
action_type: send_b2b_transfer
outcome_type: transfer_posted
claim_source: agent.actions
subject_kind: recipient
description: >
  The agent may send a transfer only within the per-transfer limit, in an allowed currency, and within the agent's
  24-hour total. The action's subject is the intended recipient (Stripe's recipient id, `acct_…`, or the profile the
  agent was told to pay, linked to it). A successful transfer must show up in Stripe as an OutboundPayment to that
  recipient created within the window and reaching `posted` (funds left the account); its amount must equal the
  amount requested. A second transfer to the same recipient within the window, a transfer that failed to confirm,
  or one that was returned by the receiving side within 30 days, fails the action.
source_citation:
  url: "https://docs.stripe.com/api/v2/money-management/outbound-payments/object"
  retrieved: "2026-10-28"
  title: "Stripe API reference — The Outbound Payment object (v2 Money Management); stripe pay CLI reference"
  notes: >
    Status values and their meaning are quoted from the reference: `processing` (created, funds held by a pending
    transaction), `posted` (confirmed, funds have left the account), `failed` (failed to confirm, funds returned by
    voiding the pending transaction), `canceled` (canceled before posting), `returned` (failed to arrive at the
    destination; funds return with a second posted transaction). The Treasury v1 object
    (https://docs.stripe.com/api/treasury/outbound_payments/object) carries the same five statuses and is read the
    same way. The `stripe pay` reference (https://docs.stripe.com/cli/pay, retrieved the same day) states that the
    command can move money, that `--yes` is to be added only after the user confirms recipient, amount, currency and
    source financial account, and that the recipient must never be guessed. Limits below are template values.
unknown_fields: [stripe_pay_object_type]
action:
  window: "1h"
  limits:
    - param_max: {param: amount, max: 10000}
    - param_in: {param: currency, values: [usd]}
  aggregate_limits:
    - aggregate_exceeds:
        source: stripe
        type: outbound_payment_created
        attr: amount
        max: 50000
        over: "24h"
        by: agent
        message: "This agent's transfers over 24 hours exceed the daily total"
  expected_effects:
    - effect_observed:
        source: stripe
        type: outbound_payment_created
        message: "No transfer to the intended recipient was created in Stripe"
    - effect_observed:
        source: stripe
        type: outbound_payment_posted
        message: "The transfer did not post: funds did not leave the account"
  forbidden_effects:
    - effect_count_exceeds: {source: stripe, type: outbound_payment_created, max: 1}
    - effect_attr_differs:
        source: stripe
        type: outbound_payment_created
        attr: amount
        equals_param: amount
        message: "The transfer amount differs from the amount requested"
    - effect_observed:
        source: stripe
        type: outbound_payment_failed
        message: "The transfer failed to confirm or was canceled before posting"
  reversed_by:
    - effect_observed:
        source: stripe
        type: outbound_payment_returned
        within: "30d"
        message: "The transfer was returned by the receiving side"
  unverifiable_if:
    - missing_fact_source: [stripe]
billing:
  unit_price: 0
  currency: USD

Use this contract See it applied in a sample verification