rail0-sdk 1.0.0 → 1.2.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: da765ab6a541e6af453972d5bf10ffc052daeac4c909bbb3ee6fb1e47ebee6fd
-  data.tar.gz: c17f6dce9b41d781e907141e77dbfbad5bc3392900c4003083cc3a0b3bb4ffb6
+  metadata.gz: 60c25c2843d57ee49df3b17267e56a612f56701d61e48430786b1c6435987eb9
+  data.tar.gz: d8ef2d01d59b1a775f116753608bba6ab90d0d868a360040c0bc8fdc64f64de0
 SHA512:
-  metadata.gz: dd490a0832f5814d3620d0d233e5d65bfa5790b9c2987e71b363fbcdf3462bb1b2d81bcb15321a2a7f72c2acf1064694c1b4ba036f35639613b54eb2ab68c787
-  data.tar.gz: e2aaf5625eb07f543d9b0429c2dbcff2333f723ebe2d44cf1b5bdb624f7df5876baff2cb437528914b18ef1270b20700df2a5cc5fb99348709875837a2587839
+  metadata.gz: e7e6441337f7daf05f4e55ba22d94a380755f5775fd203b0699e8f16029fc493c88e9863a81e2d1559e71c383db7b79330503cd724c2219dd0a1b169badfac81
+  data.tar.gz: 943a28ce8740139e30e4966ce1021b9a85271789418a2274d505a6457733a09e8cc84c3c8f435ff34962dec3ed7e5beded3fc0f7cec131de626d8e5d6535fc5d

data/README.md

@@ -15,7 +15,8 @@ lifecycle plus account, wallet, catalog, and webhook management. It mirrors the
 - Ruby ≥ 3.0
 - For SIWE login and off-chain signing: `eth` (`~> 0.5`) and `siwe-rb` (`~> 0.2`)
 
-The core HTTP client has **no runtime dependencies** (Ruby stdlib only). The `eth`
+The core HTTP client needs only the Ruby stdlib plus the `logger` gem (a declared
+dependency, since it is no longer a default gem from Ruby 4.0). The `eth`
 and `siwe-rb` gems are loaded lazily — `require "rail0"` works without them, and
 they are needed only when you call `client.auth.login` or `Rail0::Signing`.
 
@@ -126,12 +127,17 @@ client.payments.submit_by_hash(rail0_id, "capture", { transaction_hash: "0x…"
 | `charge_prepare` + `charge` | payee | One-shot authorize + capture; no escrow window |
 | `capture_prepare` + `capture` | payee | Move escrowed funds to the merchant (partial supported) |
 | `void_prepare` + `void` | payee | Cancel the hold, return funds to the payer (only before any capture) |
-| `release_prepare` + `release` | anyone | Return uncaptured escrow to the payer |
+| `release_prepare` + `release` | payer or payee | Return uncaptured escrow to the payer |
 | `refund_prepare` (phase 1+2) + `refund` | payee | Return captured funds to the payer via EIP-3009 |
 | `dispute_prepare` + `dispute` | payer | Open a dispute (signal-only) |
 | `close_dispute_prepare` + `close_dispute` | payer | Close an open dispute |
 | `dispute_submit_by_hash` / `close_dispute_submit_by_hash` | payer | Report a dispute tx the wallet already broadcast |
 
+`release` is the one merchant-side operation either participant may send: the contract
+accepts only the payer or the payee as its sender, and anyone else is refused with 422
+`release_submitter_not_a_party`. `release_prepare(id, from: "0x…")` builds the transaction
+for that sender; omitted, `from` is the signed-in caller.
+
 **Payment statuses:** `unsigned`, `signed`, `authorized`, `charged`, `captured`,
 `partially_captured`, `voided`, `released`, `refunded`, `expired` — plus
 `partially_refunded`, which is no longer produced (a partial refund deliberately leaves
@@ -141,6 +147,13 @@ exhaustive `case` that raises on it.
 `expired` is a never-captured authorization whose window lapsed. It is **not** terminal:
 the escrow is still on-chain and `release` still works from it (closing the payment as
 `released`), so treating it as closed leaves the buyer's funds where they are.
+
+How a `release` settles depends on the balances it leaves, not on the order operations
+arrived in: a total release from `authorized` or `expired` closes the payment as
+`released`; a release that leaves **both** `capturable_amount` and `refundable_amount` at
+zero (say capture 40 → refund 40 → release 60) closes it as `refunded`; any other release
+returns the escrow but leaves the status unchanged, so a captured residual stays
+refundable and disputable.
 **Transaction statuses:** `pending`, `submitting`, `submitted`, `confirmed`, `failed`.
 
 ## Authentication (SIWE)
@@ -155,9 +168,9 @@ Two role rules are worth knowing before the first call, because both surface as
 403 rather than a validation error:
 
 - `payments.create` requires the caller to **be the payer** (`payer_must_be_caller`);
-- the merchant operations (authorize, capture, charge, void, refund) are
-  **payee-only**, while `release` and the prepare steps accept either participant,
-  and `dispute`/`close_dispute` submits are **payer-only**.
+- the merchant operations (authorize, capture, charge, void, refund) and their prepare
+  steps are **payee-only**; `release` — prepare and submit — is the one that accepts
+  either participant; and `dispute`/`close_dispute` submits are **payer-only**.
 
 A wallet that signs *and broadcasts* in one step (MetaMask) reports the result by hash
 instead of handing over a signed transaction: `submit_by_hash` covers the merchant
@@ -167,7 +180,10 @@ path segments and does not fit the generic shape.
 
 ```ruby
 auth = client.auth.login(private_key: "0x…", domain: "api.rail0.xyz")
-# => { token:, address:, account_id:, name:, expires_at: }
+# => { token:, address:, account_id:, name:, expires_at:, admin: }
+# admin is always a boolean (verify too): true only for an account holding the
+# operator grant, false otherwise (visibility only). account_id/name are nil for an
+# account-less session.
 # login embeds chain_id 1 by default; pass chain_id: to match a gateway whose
 # SIWE_CHAIN_ID policy differs (e.g. login(private_key:, domain:, chain_id: 5042002)).
 
@@ -191,9 +207,9 @@ Lower-level building blocks are also available:
 
 ```ruby
 nonce   = client.auth.nonce                                  # POST /auth/nonces
-session = client.auth.verify(message: siwe_msg, signature: sig)  # POST /auth
+session = client.auth.verify(message: siwe_msg, signature: sig)  # POST /auth — same hash as login
 client.auth.logout                                           # POST /auth/logout
-client.auth.revoke_all                                       # POST /auth/revoke_all
+client.auth.revoke_all(private_key: "0x...", domain: "api.rail0.xyz")  # POST /auth/revoke_all
 ```
 
 `logout` revokes **the token this client carries**, not every session for the address —
@@ -207,19 +223,31 @@ live sessions would need five tokens you do not have. This is per **address** an
 the ones you never saw — including any an attacker is holding — which makes it the call
 for a key you no longer trust. The gateway records a cutoff **instant** rather than
 enumerating tokens, so a session minted a moment before the call is refused by its own
-`iat`; that is what makes it durable where a denylist is not. The returned `cutoff` is
-the field worth logging: it says exactly which sessions died, which `revoked: true`
-cannot.
+`iat`; that is what makes it durable where a denylist is not.
+
+It is authorized by a **fresh SIWE proof** of the address, not by the session — whoever
+is reacting to a leaked key holds the wallet, not the stolen token — so it takes the
+private key and domain (and optional `chain_id:`, default 1) exactly like `login`, and
+needs the same optional `eth`/`siwe-rb` gems. The proof carries its own statement
+(`"Sign out of RAIL0 everywhere"`), so a login signature cannot be replayed here. It is
+self-revoking: any token you hold dies too, so sign in again afterwards. It returns
+`{ revoked_all: true, cutoff_at: "<ISO-8601>" }`; `cutoff_at` is the field worth
+logging — it says exactly which sessions died, which `revoked_all: true` cannot.
 
 ## Catalog (public)
 
 ```ruby
-client.chains.list                                    # GET /blockchains
+client.chains.list                                    # GET /blockchains (each chain's :contract is the active RAIL0 deployment)
 client.chains.list(network_type: "testnet", symbol: "ETH")
-client.tokens.list                                    # GET /tokens
+client.tokens.list                                    # GET /tokens — every token, retired ones included
 client.tokens.list(chain_id: 84532, symbol: "USDC")
+client.tokens.list(active: true)                      # what a NEW payment may use
 ```
 
+`tokens.list` without `active:` is the **historical** catalogue — a payment references its
+token forever, so a retired one must still resolve. A checkout picker should pass
+`active: true`: `payments.create` answers 422 `unknown_token` for a retired token.
+
 ## Health
 
 ```ruby
@@ -230,6 +258,9 @@ client.health.get   # GET /health → { status:, api_version:, contract_version:
 
 Paginated calls return `{ data:, meta: }`. `meta` is `{ page:, per_page:, total:, total_pages:, links: }`.
 
+`page` is 1-based and bounded to 1..1,000,000 — a value outside is a 400, not an empty
+page. `per_page` defaults to 25 and is capped at 100.
+
 `total_pages` is **zero** for an empty collection — "no pages" is what there are, so a pager rendered off it renders none. `links` comes from the `Link` header: `:first` and `:last` are always present, `:prev` and `:next` only where they exist, and the hash is empty when the collection is. The URIs are **relative** (path + query) and resolve against the URL you requested — the gateway emits them that way so they cannot advertise the wrong scheme through a TLS-terminating proxy.
 
 ```ruby
@@ -267,6 +298,8 @@ account id first. `id_or_address` accepts the wallet UUID or its 0x address.
 ```ruby
 client.wallets.list(account_id, chain_id: 84532, active: true)
 # => { data: [ { id:, address:, label:, active:, tokens: [...] } ], meta: { page:, per_page:, total: } }
+# chain_id / token_symbol / default / token_active narrow the NESTED holdings, never the wallets.
+client.wallets.list(account_id, token_active: true)
 
 client.wallets.get(account_id, id_or_address)
 client.wallets.update(account_id, id_or_address, label: "Renamed", active: false)
@@ -288,13 +321,14 @@ client.wallets.create(account_id, address: "0x…", **proof, label: "Treasury")
 ```
 
 The proof is **purpose-bound**, and a login proof will not do — the gateway pins
-each endpoint to one statement and refuses the other with 422
+each endpoint to one statement and refuses the others with 422
 `siwe_purpose_mismatch`:
 
 | Endpoint | Statement | Constant |
 |---|---|---|
 | `POST /auth` | `Sign in to RAIL0` | `Rail0::Resources::Auth::LOGIN_STATEMENT` |
 | `POST /accounts/:id/wallets` | `Add this wallet to your RAIL0 account` | `Rail0::Resources::Auth::WALLET_LINK_STATEMENT` |
+| `POST /auth/revoke_all` | `Sign out of RAIL0 everywhere` | `Rail0::Resources::Auth::REVOKE_ALL_STATEMENT` |
 
 That is a security boundary rather than a label: a login signature is handed out
 on every sign-in, so a wallet-link endpoint that accepted one would let anyone
@@ -305,14 +339,20 @@ buyers, so it is the last step of merchant onboarding:
 
 ```ruby
 holding = client.wallets.add_token(account_id, id_or_address, chain_id: 84532, token: "0x…", default: true)
-client.wallets.enable_token(account_id, id_or_address, holding[:id])
-client.wallets.disable_token(account_id, id_or_address, holding[:id])  # keeps the holding
-client.wallets.remove_token(account_id, id_or_address, holding[:id])   # 204, soft delete
+client.wallets.enable_token(account_id, id_or_address, holding[:token_id])
+client.wallets.disable_token(account_id, id_or_address, holding[:token_id])  # keeps the holding
+client.wallets.remove_token(account_id, id_or_address, holding[:token_id])   # 204, soft delete
 ```
 
 `add_token` is idempotent by (wallet, chain, token): re-adding an existing holding
 re-enables it and answers 200 instead of creating a second row. The id passed to
-the other three is the **holding's** id, not the token address.
+the other three is the **token's** UUID (`token_id` on the holding), not an id of the
+holding row and not the token address — the gateway looks the holding up by (wallet, token).
+
+The wallet's active **default** holding cannot be disabled or removed — that would leave it
+with no preferred payment method — and the gateway answers 422 `default_payment_method`.
+Make another token the default first (`add_token(..., default: true)` demotes the old one
+in the same transaction), then disable or remove it.
 
 ## Payments
 
@@ -322,7 +362,9 @@ client.payments.create(params, idempotency_key: nil)  # or keyword fields
 # "idempotency_key_reused" (422) instead of returning the first payment.
 client.payments.get(id)
 client.payments.list(status: "authorized", disputed: false, chain_id: 84532, sort: "-created_at")
+client.payments.list(operation: "refund")            # payments with at least one refund transaction
 client.payments.transactions(id, operation: "capture")
+# `operation` on both takes Payments::TRANSACTION_OPERATIONS — dispute and close_dispute included.
 client.payments.redrive(id, transaction_id)           # re-enqueue a stuck broadcast
 # Offer `redrive` on the row's `redrivable` flag — the same predicate the gateway guards
 # the route with — and not on `status == "pending"`: a pending row holding no signed
@@ -365,8 +407,11 @@ client.payments.refund(rail0_id, { signed_transaction: raw })
 
 ### Disputes (payer-driven)
 
-Disputes are authorized on-chain by the payer (no JWT) and follow the same
-prepare → submit pattern:
+> **Operations go through the gateway.** The gateway mirrors only the operations it prepared. A dispute, close-dispute, capture, void, refund or release sent to the RAIL0 contract directly — outside this SDK's prepare/submit calls — happens on-chain, but the payment's status and balances on the gateway do not change and no webhook is sent; a merchant is not told about a dispute its buyer opened that way. The gateway records it for its operators as a sync error (`external_operation`).
+
+Disputes are signed on-chain by the payer and follow the same prepare → submit
+pattern. Like the rest of `/payments` they need a session, but the payer's
+account-less SIWE login is enough:
 
 ```ruby
 prep = client.payments.dispute_prepare(rail0_id, reason: "0x…") # reason optional
@@ -411,10 +456,18 @@ client.webhooks.enable(id)
 client.webhooks.disable(id)
 client.webhooks.rotate_secret(id)    # returns a fresh shared_secret
 client.webhooks.reset_circuit(id)
-client.webhooks.event_callbacks(id, status: "failed")
+# status is "delivered" or "failed" only; payment_id takes a UUID or a rail0_id.
+client.webhooks.event_callbacks(id, status: "failed", response_code: "500")
+client.webhooks.redeliver(id, callback_id)  # 202 { status: "queued" } — replay one delivery
 client.webhooks.delete(id)           # 204
 ```
 
+`redeliver` replays a recorded delivery's exact payload — the same event id, so a receiver
+that already processed it deduplicates — under a fresh signature. It is the way back for
+events lost while the circuit breaker was open. Delivery is async and the dispatcher drops
+anything for an inactive webhook, so `enable` (if disabled) or `reset_circuit` (if the
+breaker opened) **first**, or the 202 is answered and the replay silently dropped.
+
 ### Verifying a delivery
 
 Every delivery carries `X-Rail0-Topic`, `X-Rail0-Timestamp` and
@@ -456,9 +509,19 @@ digest with it. Comparison is constant-time.
 client.accounts.get(account_id)
 # => { id: "019f…", name: "Test Merchant", email: "merchant@rail0.test",
 #      created_at: "2026-08-01T00:00:00Z", updated_at: "2026-08-20T00:00:00Z" }
+
+# Update the same profile — only the fields passed are sent.
+client.accounts.update(account_id, email: "ops@merchant.example")
+client.accounts.update(account_id, name: "Merchant Ltd", email: "ops@merchant.example")
 ```
 
 `email` is in the response because the holder is this endpoint's only possible caller.
+
+`update` needs at least one of `name`/`email` (it raises `ArgumentError` before sending an
+empty PATCH, which the gateway would answer with 400). Both are unique across accounts, so
+a value another account holds answers **409**. It is a write on the account, so a
+deactivated wallet (403 `wallet_deactivated`) or account (403 `account_deactivated`) cannot
+make it. The gateway's `active` field is operator-only and not exposed here.
 The account's wallets are a collection under the same path (`client.wallets`), and
 buyer-facing discovery is `client.payment_methods`.
 
@@ -529,9 +592,17 @@ client.analytics.breakdown(by: "operation")
 # => [{ key: "capture", orders: 1, transactions: 2 }, …]
 ```
 
-All three take the same filters — `mode`, `status`, `token`, `chain_id`, `from`, `to` — so
-the same question can be asked at three resolutions: one total, a series over time, a split
-by dimension. `from`/`to` filter the payment's CREATION date, which matters when reading
+All three take the same filters — `mode`, `status`, `token`, `chain_id`, `from`, `to`,
+`payee` — so the same question can be asked at three resolutions: one total, a series over
+time, a split by dimension. Figures cover all of the account's wallets unless `payee` pins
+one of them (a 0x address the account owns — another address is refused with 403, a
+malformed one with 400):
+
+```ruby
+client.analytics.summary(payee: "0xYourWallet…")
+```
+
+`from`/`to` filter the payment's CREATION date, which matters when reading
 gas: a payment created in one period and captured in the next books its capture gas in the
 first.
 
@@ -621,8 +692,7 @@ end
 ```
 
 **`error` is the only field to branch on.** It is the specific condition, read from the
-gateway's `code` and falling back to the older `error` sub-code and then to `status` (the
-wider family), so an older gateway still yields the most specific value it sent.
+gateway's `code`.
 
 `title` and `detail` come from the gateway's error catalogue, so the same condition always
 reads the same way whichever endpoint surfaced it; `detail` is written to be shown to a
@@ -661,8 +731,8 @@ Rail0::Client.new(
 ### Rate limits
 
 The gateway throttles two surfaces independently: the public, unauthenticated one **per
-IP** (100 requests / 60s by default — SIWE nonce + verify, `/payment_methods`, the
-catalog reads, `/health`) and everything authenticated **per session**, keyed on the
+IP** (100 requests / 60s by default — SIWE nonce + verify, `/auth/revoke_all`,
+`/payment_methods`, the catalog reads, `/health`) and everything authenticated **per session**, keyed on the
 JWT's subject (300 / 60s). Over budget it answers **429** with `code: "rate_limited"` and
 a `Retry-After`.
 
@@ -678,8 +748,8 @@ rescue Rail0::ApiError => e
 end
 ```
 
-Note what the number means: the gateway sends **the whole throttle period**, not the time
-left in the current window, so it is an upper bound on the wait rather than a measurement.
+Note what the number means: the gateway sends **the time left in the current window**
+(the same value as `RateLimit-Reset`), not the window's length, so it is the wait itself.
 
 `retry_on_429: true` makes the SDK do that waiting for you — Retry-After, clamped to
 `retry_after_cap`, plus a little jitter (see `Rail0::Backoff`; callers sharing one session
@@ -709,6 +779,8 @@ lib/rail0/
   default_logger.rb    Rail0::LogEntry + Rail0::DefaultLogger (Logger subclass) for `logger:`
   api_error.rb         Rail0::ApiError (code/title/detail + #hint)
   error_hints.rb       Rail0.describe_error — per-code next steps, shared with the other SDKs
+  backoff.rb           Rail0::Backoff — retry delays and 429 jitter
+  webhook_signature.rb Rail0::WebhookSignature — delivery verification
   signing.rb           EIP-3009 + EIP-1559 signing (requires 'eth')
   stablecoins.rb       stablecoin address registry
   types.rb             generated Struct docs of the gateway schema (reference only)
@@ -721,6 +793,8 @@ lib/rail0/
     payment_methods.rb public payment-method discovery
     wallets.rb         account-scoped wallet management (JWT)
     payments.rb        payment lifecycle + disputes
+    disputes.rb        account-level dispute listing (JWT)
+    accounts.rb        the caller's own account profile, read and update (JWT)
     webhooks.rb        webhook subscription management (JWT)
     analytics.rb       account-scoped payment analytics (JWT)
     query.rb           shared query-string helper
@@ -748,6 +822,26 @@ uses them everywhere, table-aligned hashes because some literals are tables, and
 (`retry_on_429`, `eip712`, `secp256k1`) that each spell themselves their own way. A linter
 that argues with the codebase teaches people to ignore it.
 
+## Publishing
+
+Releases publish from GitHub Actions (`.github/workflows/release.yml`) through RubyGems
+**Trusted Publishing**: RubyGems.org trusts that workflow in this repo, so there is no API
+key to store or rotate and no OTP prompt.
+
+1. Merge a PR that bumps `Rail0::VERSION` in `lib/rail0/version.rb`.
+2. Publish a GitHub release on `main` tagged `v<version>` (e.g. `v1.2.0`).
+
+The workflow checks the tag against `Rail0::VERSION`, runs `rake build` (rubocop and the
+specs first, then the gem) and pushes it. A version already on RubyGems.org is skipped, so
+a re-run (Actions → release → Run workflow, from `main`, with the tag as input) is always
+safe — that is also how a release cut before the workflow existed gets published.
+
+One-time setup, by an owner of the gem on rubygems.org: rail0-sdk → Trusted publishers →
+GitHub Actions, repository `commercelayer/rail0-ruby`, workflow `release.yml`.
+
+Publishing by hand still works as a fallback (`gem build rail0-sdk.gemspec && gem push
+rail0-sdk-<version>.gem`, with the OTP the gem's `rubygems_mfa_required` asks for).
+
 ## License
 
 [MIT](LICENSE)

data/lib/rail0/api_error.rb

@@ -21,9 +21,10 @@ module Rail0
     #     otherwise. Surfaced because the alternative is a caller guessing: the SDK used
     #     to drop the header, so "rate limited" arrived with no idea of for how long.
     #
-    #     Note it is the WHOLE window the gateway throttles over, not the time left in it
-    #     — the limiter sends its period verbatim — so it is an upper bound on the wait,
-    #     not a measurement. Rail0::Backoff clamps it for that reason.
+    #     It is the time LEFT in the current throttle window, not the window's length:
+    #     the limiter buckets by wall clock, so the gateway computes the remainder exactly
+    #     (the same number it sends as RateLimit-Reset). Rail0::Backoff still clamps it,
+    #     against a hostile or misconfigured value from anything in between.
     attr_reader :status, :error, :title, :detail, :retry_after
 
     # @param status [Integer]

data/lib/rail0/backoff.rb

@@ -24,11 +24,10 @@ module Rail0
   #    per-session bucket and would all be told the same Retry-After, wake together, and
   #    recreate the burst the limiter just rejected.
   #
-  # 2. THE CAP IS NOT PARANOIA. The gateway sends the WHOLE period as Retry-After
-  #    (rack_attack.rb: `headers["retry-after"] = match_data[:period].to_s`), not the time
-  #    remaining in the window — so hitting the limit one second in is told to wait the
-  #    full 60. Capping bounds both that over-wait and a hostile or misconfigured value
-  #    from anything between the client and the gateway.
+  # 2. THE CAP IS NOT PARANOIA. The gateway sends the time LEFT in the throttle window as
+  #    Retry-After (it used to send the whole period, which over-waited by up to a full
+  #    window). Even an exact number comes through whatever sits between the client and
+  #    the gateway, so capping bounds a hostile or misconfigured value.
   module Backoff
     module_function
 

data/lib/rail0/error_hints.rb

@@ -51,6 +51,11 @@ module Rail0
     "not_payee" => "only the merchant (payee) may do this",
     "not_payer" => "only the buyer (payer) may do this",
     "not_payer_or_payee" => "only the payer or the payee may do this",
+    "release_submitter_not_a_party" => "a release must be sent by the payment's payer or payee — omit `from` to build it for the signed-in wallet",
+    "payer_must_be_caller" => "the payer must be the signed-in wallet — sign in as the buyer to create its payment",
+    "wallet_deactivated" => "this wallet is deactivated: it can still read, but not act on payments or change the account — reactivate it or sign in with another of the account's wallets",
+    "account_deactivated" => "the merchant account is deactivated: void, release and refund still work, but authorize, charge, capture and account changes do not — ask an operator to reactivate it",
+    "not_redrivable" => "only a pending transaction that already holds its signed bytes can be redriven — check the transaction's `redrivable` flag, and submit the signature if it has none",
     "refund_expired" => "the refund window has closed (refundExpiry passed) — refund/dispute is no longer possible",
     "authorization_not_expired" => "release opens only after authorizationExpiry — wait until it passes",
     "already_captured" => "already (partially) captured — use release for the remainder, not void",
@@ -63,9 +68,10 @@ module Rail0
     "no_active_contract" => "no active RAIL0 contract on that chain",
     "missing_param" => "a required parameter is missing from the request",
     # A BARE forbidden is not a party mismatch: the gateway split those into codes of
-    # their own (not_the_payee, not_the_payer, wallet_deactivated, not_your_account)
-    # because they need different fixes. This entry kept describing one of them long
-    # after the split — and the rule it named no longer exists in the gateway at all.
+    # their own (not_the_payee, not_the_payer, wallet_deactivated, account_deactivated,
+    # not_your_account) because they need different fixes. This entry kept describing
+    # one of them long after the split — and the rule it named no longer exists in the
+    # gateway at all.
     "forbidden" => "not permitted for this session — typically the operator grant, a resource owned by another account, or a transaction signed by the wrong wallet"
   }.freeze
 

data/lib/rail0/http_client.rb

@@ -17,8 +17,8 @@ module Rail0
     #   It does NOT need `max_retries` to be set as well. That pairing is a footgun —
     #   the flag would silently do nothing — so on its own it allows one retry.
     # @param retry_after_cap [Numeric] longest wait to honour, in seconds. The gateway
-    #   sends its whole throttle period as Retry-After rather than the time left in it,
-    #   so this bounds both the over-wait and any hostile value from in between.
+    #   sends the time left in its throttle window as Retry-After; this bounds any
+    #   hostile or misconfigured value from in between.
     def initialize(base_url:, headers: {}, token: nil, timeout: 30, logger: nil,
                    max_retries: 0, retry_delay: 0.2, retry_on_429: false,
                    retry_after_cap: 60)

data/lib/rail0/resources/accounts.rb

@@ -4,12 +4,14 @@ module Rail0
   module Resources
     # The merchant account itself (requires JWT).
     #
-    # One method, and that is the whole surface by design: the gateway guards
-    # `/accounts/:account_id` with an ownership check — a JWT whose account matches the
-    # path — so a caller can only ever read its OWN account. There is no endpoint for
-    # reading another merchant's, and an id that is not an account answers 404 exactly as
-    # another account's id does, so the pair cannot be used to learn whether an account
-    # exists.
+    # Read and update. The gateway guards `/accounts/:account_id` with an
+    # owner-or-operator check: a merchant session reaches only its OWN account, and an
+    # operator (an admin session) may reach any. For anyone else another account's id
+    # answers the same 403 `not_your_account` as a plain ownership miss, so the pair
+    # cannot be used to learn whether an account exists.
+    #
+    # The gateway's PATCH also takes `active`, but that field is the OPERATOR's (an owner
+    # sending it gets 403), so it is deliberately not exposed here.
     #
     # The account's wallets are a collection under the same path and live on
     # {Resources::Wallets}; buyer-facing discovery of what a merchant accepts lives on
@@ -25,11 +27,36 @@ module Rail0
       # The account's own profile.
       # @param account_id [String] The account UUID — must be the one this JWT belongs to.
       # @return [Hash] `id`, `name`, `email`, `created_at`, `updated_at`. `email` is part of
-      #   the response because the holder is this endpoint's only possible caller: it is a
-      #   merchant reading its own contact address, never another's.
+      #   the response because only the account's owner, or an operator, can read it.
       def get(account_id)
         http.get("/accounts/#{account_id}")
       end
+
+      # Update the account's own profile (PATCH /accounts/:account_id).
+      #
+      # Only the fields passed are sent, and at least one is required: a PATCH with
+      # nothing to change is a caller bug, which the gateway answers with 400 — so this
+      # raises ArgumentError first rather than spending a request on it. Both fields are
+      # UNIQUE across accounts, so a value another account already holds answers 409.
+      #
+      # This is a write on the account itself, so a deactivated wallet (403
+      # wallet_deactivated) or a deactivated account (403 account_deactivated) cannot
+      # make it: a revoked key must not be able to redirect the contact address where
+      # the merchant's operational notifications go.
+      #
+      # @param account_id [String] The account UUID — must be the one this JWT belongs to.
+      # @param name [String, nil] New display name (non-blank; unique across accounts).
+      # @param email [String, nil] New contact email (non-blank; unique across accounts).
+      # @return [Hash] the updated profile, same shape as {get}.
+      # @raise [ArgumentError] when neither name nor email is given.
+      def update(account_id, name: nil, email: nil)
+        body = {}
+        body[:name]  = name  unless name.nil?
+        body[:email] = email unless email.nil?
+        raise ArgumentError, "at least one of name or email is required" if body.empty?
+
+        http.patch("/accounts/#{account_id}", body)
+      end
     end
   end
 end

data/lib/rail0/resources/analytics.rb

@@ -16,13 +16,15 @@ module Rail0
     # chain: it is denominated in the chain's native token, so it is reported per chain and
     # never totalled.
     #
+    # Figures cover every wallet of the account unless `payee` pins one of them.
+    #
     # These methods return the parsed JSON as-is, so the keys documented below are the
     # contract this SDK offers — there is no typed wrapper standing between them and the
     # gateway.
     class Analytics
       include Query
 
-      FILTERS = %i[mode status token chain_id from to].freeze
+      FILTERS = %i[mode status token chain_id from to payee].freeze
 
       attr_reader :http
 
@@ -38,6 +40,10 @@ module Rail0
       # @param chain_id [Integer, nil] Chain ID. Pass nil or 0 for all chains.
       # @param from [String, nil] ISO-8601 — payments created at/after this time.
       # @param to [String, nil] ISO-8601 — payments created at/before this time.
+      # @param payee [String, nil] One of the account's wallet addresses (0x…) — scopes the
+      #   figures to that wallet instead of all the account's wallets. The gateway refuses an
+      #   address the account does not own (403) and a malformed one (400). Accepted by all
+      #   three views.
       # @return [Hash] the headline KPIs:
       #   * `orders`, `disputed` — counts.
       #   * `refund_rate`, `dispute_rate` — fractions in [0,1], per ORDER.
@@ -95,7 +101,7 @@ module Rail0
       #   often the operation ran — a partial capture runs several times on one order — and
       #   `orders` is how many orders it touched.
       def breakdown(by:, **filters)
-        raise ArgumentError, "by is required (token, chain, mode or status)" if by.nil? || by.to_s.empty?
+        raise ArgumentError, "by is required (token, chain, mode, status or operation)" if by.nil? || by.to_s.empty?
 
         http.get("/analytics/breakdown#{build_query(**only_filters(filters), by: by)}")
       end

data/lib/rail0/resources/auth.rb

@@ -31,6 +31,13 @@ module Rail0
       # account. Never collapse the two into a single constant.
       WALLET_LINK_STATEMENT = "Add this wallet to your RAIL0 account"
 
+      # The SIWE statement for revoking every session of an address —
+      # POST /auth/revoke_all. The gateway asserts it exactly
+      # (Policy::SIWE_REVOKE_ALL_STATEMENT) for the reason the other two are
+      # separate: a proof is spendable at exactly one endpoint, so a captured login
+      # signature cannot be replayed to sign its address out everywhere.
+      REVOKE_ALL_STATEMENT = "Sign out of RAIL0 everywhere"
+
       attr_reader :http
 
       def initialize(http)
@@ -47,9 +54,15 @@ module Rail0
       # Submit a pre-built SIWE message and its signature, returning a JWT.
       # @param message   [String] EIP-4361 formatted message string.
       # @param signature [String] 0x-prefixed hex signature.
-      # @return [Hash] { token:, address:, account_id:, name:, expires_at: }
+      # @return [Hash] { token:, address:, account_id:, name:, expires_at:, admin: }
+      #
+      # +admin+ is true only for an account holding the operator (administrators)
+      # grant: the gateway adds the field on an admin's session alone, and it is
+      # normalised here to a boolean so a standard login reads false rather than nil.
+      # Visibility only — every gated route re-checks the grant per request.
       def verify(message:, signature:)
-        http.post("/auth", { message: message, signature: signature })
+        session = http.post("/auth", { message: message, signature: signature })
+        session.merge(admin: session[:admin] == true)
       end
 
       # End the session whose token this client carries.
@@ -70,23 +83,43 @@ module Rail0
         http.post("/auth/logout", {})
       end
 
-      # End EVERY session of the calling address (POST /auth/revoke_all).
+      # End EVERY session of the address controlled by +private_key+
+      # (POST /auth/revoke_all).
       #
       # The answer to a key you no longer trust, and {#logout} cannot be that answer: it
       # is per TOKEN, so an address with five live sessions needs five tokens the caller
       # does not have. This is per ADDRESS and reaches the ones it never saw — including
       # any an attacker is holding.
       #
+      # Authorized by a FRESH SIWE PROOF of the address, not by the session: someone
+      # reacting to a leaked key holds the wallet, not the stolen token, so requiring the
+      # session would make this useless exactly when it is needed. The proof is the same
+      # handshake as {#login} — fetch a single-use nonce, build an EIP-4361 message, sign
+      # it with EIP-191 personal_sign — but carries {REVOKE_ALL_STATEMENT}, so a login
+      # proof cannot be replayed here (the gateway answers 422 siwe_purpose_mismatch).
+      # This method used to post an empty body, which the gateway refused on every call,
+      # and read `revoked`/`cutoff`, which the gateway never sends.
+      #
       # The gateway records a cutoff INSTANT rather than enumerating tokens, so a session
-      # minted a moment before the call is refused by its own `iat`. That is what makes it
-      # durable where a denylist is not: there is nothing to enumerate and nothing to miss.
+      # minted a moment before the call is refused by its own `iat`. It is self-revoking:
+      # the cutoff is just after now, so any token this caller holds dies with the rest —
+      # sign in again afterwards. (The client does not store the JWT, so there is nothing
+      # local to clear; drop your own copy.)
       #
-      # `cutoff` is the field worth logging. It says exactly which sessions died, which
-      # `revoked: true` cannot.
+      # `cutoff_at` is the field worth logging. It says exactly which sessions died, which
+      # `revoked_all: true` cannot.
       #
-      # @return [Hash] { revoked: true|false, cutoff: "2026-08-27T21:00:00Z" }
-      def revoke_all
-        http.post("/auth/revoke_all", {})
+      # Requires the optional 'eth' and 'siwe-rb' gems.
+      #
+      # @param private_key [String] 0x-prefixed hex private key of the address to sign out.
+      # @param domain      [String] Host of the API server (e.g. "api.rail0.xyz").
+      # @param chain_id    [Integer] Chain ID to embed; same meaning and default as #login.
+      # @return [Hash] { revoked_all: true, cutoff_at: "2026-09-24T18:00:01Z" } — cutoff_at
+      #   is an ISO-8601 instant; every token of the address issued before it is refused.
+      def revoke_all(private_key:, domain:, chain_id: 1)
+        message, signature = sign_proof(private_key, domain, chain_id, REVOKE_ALL_STATEMENT)
+        result = http.post("/auth/revoke_all", { message: message, signature: signature })
+        { revoked_all: result[:revoked_all], cutoff_at: result[:cutoff_at] }
       end
 
       # Perform the full SIWE authentication flow:
@@ -102,7 +135,7 @@ module Rail0
       # @param chain_id    [Integer] Chain ID to embed in the SIWE message. Must match
       #   the gateway's SIWE_CHAIN_ID policy (default 1); override only when the
       #   gateway is configured with a different login chain.
-      # @return [Hash] { token:, address:, account_id:, name:, expires_at: }
+      # @return [Hash] { token:, address:, account_id:, name:, expires_at:, admin: }
       def login(private_key:, domain:, chain_id: 1)
         message, signature = sign_proof(private_key, domain, chain_id, LOGIN_STATEMENT)
         verify(message: message, signature: signature)
@@ -135,9 +168,9 @@ module Rail0
 
       private
 
-      # The shared core of both handshakes. Everything but the STATEMENT is
-      # identical, which is precisely why the statement is a parameter and never a
-      # default — see the note on the two constants.
+      # The shared core of every SIWE handshake (login, prove_address, revoke_all).
+      # Everything but the STATEMENT is identical, which is precisely why the
+      # statement is a parameter and never a default — see the note on the constants.
       def sign_proof(private_key, domain, chain_id, statement)
         ensure_signing_deps!
 

data/lib/rail0/resources/chains.rb

@@ -20,7 +20,9 @@ module Rail0
       # @param symbol [String, nil] Filter by native symbol (case-insensitive, e.g. "ETH").
       # @return [Array<Hash>] chain_id, name, native_symbol, network_type, explorer_url,
       #   required_confirmations, finality_tag (the settlement rule: the tag where the
-      #   chain serves one, the count only where it does not)
+      #   chain serves one, the count only where it does not), and contract — the chain's
+      #   active RAIL0 deployment as `{ address:, version:, deployed_at: }` (what holds
+      #   the money; nullable in principle, present in practice)
       def list(network_type: nil, symbol: nil)
         http.get("/blockchains#{build_query(network_type: network_type, symbol: symbol)}")
       end

data/lib/rail0/resources/disputes.rb

@@ -23,7 +23,7 @@ module Rail0
       # List the account's disputes.
       # @param status [String, nil] Filter by "open" or "closed".
       # @param sort [String, nil] Comma-separated sort fields; prefix with - for desc.
-      # @param page [Integer, nil] Page number (1-based).
+      # @param page [Integer, nil] Page number (1-based; 1..1,000,000, 400 outside).
       # @param per_page [Integer, nil] Items per page (max 100).
       # @return [Hash] { data: Array<Hash>, meta: { page:, per_page:, total: } }
       def list(status: nil, sort: nil, page: nil, per_page: nil)

data/lib/rail0/resources/payments.rb

@@ -18,6 +18,11 @@ module Rail0
       # Operations accepted by the prepare/submit endpoints.
       OPERATIONS = %w[authorize capture charge void release refund].freeze
 
+      # Every operation a transaction row can carry — a superset of {OPERATIONS}, since
+      # dispute/close_dispute have routes of their own. The values the `operation`
+      # filters on {list} and {transactions} accept.
+      TRANSACTION_OPERATIONS = (OPERATIONS + %w[dispute close_dispute]).freeze
+
       attr_reader :http
 
       def initialize(http)
@@ -35,6 +40,8 @@ module Rail0
       # @param rail0_id [String, nil] Filter by the logical on-chain payment id (0x…).
       # @param chain_id [Integer, nil] Filter by the payment's chain.
       # @param disputed [Boolean, nil] Filter by whether an open dispute exists.
+      # @param operation [String, nil] Only payments carrying at least one transaction with
+      #   this operation (see {TRANSACTION_OPERATIONS}).
       # @param min_amount [String, nil] Minimum amount in token BASE UNITS (inclusive).
       # @param max_amount [String, nil] Maximum amount in token BASE UNITS (inclusive).
       #   These two really are base units — the filter runs against the stored column.
@@ -43,14 +50,15 @@ module Rail0
       # @param created_from [String, nil] Only payments created at/after this ISO-8601 time.
       # @param created_to [String, nil] Only payments created at/before this ISO-8601 time.
       # @param sort [String, nil] Comma-separated sort fields; prefix with - for desc.
-      # @param page [Integer, nil] Page number (1-based).
+      # @param page [Integer, nil] Page number (1-based; 1..1,000,000, 400 outside).
       # @param per_page [Integer, nil] Items per page (max 100).
       # @return [Hash] { data: Array<Hash>, meta: { page:, per_page:, total: } }
       def list(status: nil, mode: nil, payer: nil, payee: nil, token: nil, rail0_id: nil,
-               chain_id: nil, disputed: nil, min_amount: nil, max_amount: nil,
+               chain_id: nil, disputed: nil, operation: nil, min_amount: nil, max_amount: nil,
                created_from: nil, created_to: nil, sort: nil, page: nil, per_page: nil)
         query = build_query(status: status, mode: mode, payer: payer, payee: payee, token: token,
                             rail0_id: rail0_id, chain_id: chain_id, disputed: disputed,
+                            operation: operation,
                             min_amount: min_amount, max_amount: max_amount,
                             created_from: created_from, created_to: created_to,
                             sort: sort, page: page, per_page: per_page)
@@ -87,10 +95,11 @@ module Rail0
 
       # List on-chain transactions for a payment.
       # @param id [String] Payment UUID or rail0_id.
-      # @param operation [String, nil] Filter by operation (see {OPERATIONS}).
+      # @param operation [String, nil] Filter by operation (see {TRANSACTION_OPERATIONS} —
+      #   dispute and close_dispute included).
       # @param status [String, nil] Filter by transaction status.
       # @param sort [String, nil] Comma-separated sort fields; prefix with - for desc.
-      # @param page [Integer, nil] Page number (1-based).
+      # @param page [Integer, nil] Page number (1-based; 1..1,000,000, 400 outside).
       # @param per_page [Integer, nil] Items per page (max 100).
       # @return [Hash] { data: Array<Hash>, meta: { page:, per_page:, total: } }
       def transactions(id, operation: nil, status: nil, sort: nil, page: nil, per_page: nil)
@@ -149,7 +158,7 @@ module Rail0
       # @param id [String] Payment UUID or rail0_id.
       # @param status [String, nil] Filter by dispute status ("open" or "closed").
       # @param sort [String, nil] Comma-separated sort fields; prefix with - for desc.
-      # @param page [Integer, nil] Page number (1-based).
+      # @param page [Integer, nil] Page number (1-based; 1..1,000,000, 400 outside).
       # @param per_page [Integer, nil] Items per page (max 100).
       # @return [Hash] { data: Array<Hash>, meta: { page:, per_page:, total: } }
       def disputes(id, status: nil, sort: nil, page: nil, per_page: nil)
@@ -239,9 +248,10 @@ module Rail0
         submit(id, "void", params)
       end
 
-      # Phase 1 — build the unsigned release() transaction. +from+ overrides the
-      # submitter address (defaults to the payer). Returns uncaptured escrow to the
-      # payer.
+      # Phase 1 — build the unsigned release() transaction for +from+, whose nonce it
+      # carries. +from+ must be the payment's payer or payee (the gateway answers 422
+      # release_submitter_not_a_party otherwise); omitted, it is the signed-in caller.
+      # Returns uncaptured escrow to the payer.
       def release_prepare(id, from: nil, idempotency_key: nil)
         prepare(id, "release", from ? { from: from } : {}, idempotency_key: idempotency_key)
       end

data/lib/rail0/resources/tokens.rb

@@ -15,13 +15,20 @@ module Rail0
         freeze
       end
 
-      # List active tokens, optionally filtered by chain and/or symbol.
+      # List tokens, optionally filtered by chain, symbol and/or active flag.
+      #
+      # Without `active:` this is the HISTORICAL catalogue — retired tokens included — so
+      # a payment created long ago still resolves its token. Only an active token may be
+      # used for a NEW payment (POST /payments answers 422 unknown_token otherwise), so a
+      # checkout picker should pass `active: true`.
+      #
       # @param chain_id [Integer, nil] Chain ID to filter by. Pass nil or 0 for all chains.
       # @param symbol [String, nil] Filter by token symbol (case-insensitive, e.g. "USDC").
-      # @return [Array<Hash>] chain_id, symbol, address, decimals
-      def list(chain_id: nil, symbol: nil)
+      # @param active [Boolean, nil] Filter by active flag; omitted returns every token.
+      # @return [Array<Hash>] chain_id, symbol, address, decimals, active
+      def list(chain_id: nil, symbol: nil, active: nil)
         chain_id = nil if chain_id == 0
-        http.get("/tokens#{build_query(chain_id: chain_id, symbol: symbol)}")
+        http.get("/tokens#{build_query(chain_id: chain_id, symbol: symbol, active: active)}")
       end
     end
   end

data/lib/rail0/resources/wallets.rb

@@ -27,14 +27,17 @@ module Rail0
       # @param token_symbol [String, nil] Restrict nested tokens to this symbol (e.g. "USDC").
       # @param active [Boolean, nil] Filter wallets by active flag.
       # @param default [Boolean, nil] Restrict nested holdings to the default one.
+      # @param token_active [Boolean, nil] Restrict nested holdings to this active status
+      #   (does not hide wallets). Omitted returns holdings whatever their flag.
       # @param sort [String, nil] Comma-separated sort fields; prefix with - for desc.
-      # @param page [Integer, nil] Page number (1-based).
+      # @param page [Integer, nil] Page number (1-based; 1..1,000,000, 400 outside).
       # @param per_page [Integer, nil] Items per page (max 100).
       # @return [Hash] { data: Array<Hash>, meta: { page:, per_page:, total: } }
       def list(account_id, chain_id: nil, token_symbol: nil, active: nil, default: nil,
-               sort: nil, page: nil, per_page: nil)
+               token_active: nil, sort: nil, page: nil, per_page: nil)
         query = build_query(chain_id: chain_id, token_symbol: token_symbol, active: active,
-                            default: default, sort: sort, page: page, per_page: per_page)
+                            default: default, token_active: token_active,
+                            sort: sort, page: page, per_page: per_page)
         http.get_list("/accounts/#{account_id}/wallets#{query}")
       end
 
@@ -135,8 +138,15 @@ module Rail0
 
       # Stop accepting a token on this wallet (soft delete). Returns HTTP 204.
       #
-      # `token_id` is the id of the HOLDING as returned by {add_token} / {list}'s
-      # nested `tokens`, not the token's contract address.
+      # `token_id` is the TOKEN's UUID — the `token_id` field on a holding returned
+      # by {add_token} / {list}'s nested `tokens` — not an id of the holding row and
+      # not the token's contract address. The gateway looks the holding up by
+      # (wallet, token_id); the same applies to {enable_token} and {disable_token}.
+      #
+      # The wallet's active DEFAULT holding cannot be removed: that would leave it with no
+      # preferred payment method and nothing saying so, and the gateway answers 422
+      # default_payment_method. Make another token the default first ({add_token} with
+      # `default: true` demotes this one in the same transaction), then remove it.
       #
       # @return [nil]
       def remove_token(account_id, id_or_address, token_id)
@@ -151,6 +161,9 @@ module Rail0
 
       # Disable an existing token holding without forgetting it — the holding (and
       # its default flag) survives, so re-enabling restores the previous setup.
+      #
+      # Like {remove_token}, refused with 422 default_payment_method for the wallet's
+      # active default holding — promote another token to default first.
       # @return [Hash] the token holding
       def disable_token(account_id, id_or_address, token_id)
         http.patch("/accounts/#{account_id}/wallets/#{id_or_address}/tokens/#{token_id}/disable")

data/lib/rail0/resources/webhooks.rb

@@ -45,7 +45,7 @@ module Rail0
       # @param active [Boolean, nil] Filter by active flag.
       # @param circuit_state [String, nil] Filter by circuit state ("closed" or "open").
       # @param sort [String, nil] Comma-separated sort fields; prefix with - for desc.
-      # @param page [Integer, nil] Page number (1-based).
+      # @param page [Integer, nil] Page number (1-based; 1..1,000,000, 400 outside).
       # @param per_page [Integer, nil] Items per page (max 100).
       # @return [Hash] { data: Array<Hash>, meta: { page:, per_page:, total: } }
       def list(topic: nil, active: nil, circuit_state: nil, sort: nil, page: nil, per_page: nil)
@@ -119,22 +119,50 @@ module Rail0
 
       # List delivery attempts for a webhook.
       # @param id [String] Webhook UUID.
-      # @param status [String, nil] Filter by delivery status ("pending", "delivered", "failed").
+      # @param status [String, nil] Filter by delivery status: "delivered" or "failed" only
+      #   (anything else, "pending" included, is a 400).
       # @param topic [String, nil] Filter by event topic.
-      # @param payment_id [String, nil] Filter by the payment the delivery is for.
+      # @param payment_id [String, nil] Filter by the payment the delivery is for: its UUID
+      #   or its rail0_id (0x…). One that names no payment matches nothing rather than erroring.
+      # @param response_code [String, Integer, nil] Filter by the subscriber's exact HTTP
+      #   response code (e.g. 500) — `status: "failed"` finds the failures, this says which.
       # @param since [String, nil] Only deliveries at/after this ISO-8601 time.
       # @param until_time [String, nil] Only deliveries at/before this ISO-8601 time (query key: "until").
       # @param sort [String, nil] Comma-separated sort fields; prefix with - for desc.
-      # @param page [Integer, nil] Page number (1-based).
+      # @param page [Integer, nil] Page number (1-based; 1..1,000,000, 400 outside).
       # @param per_page [Integer, nil] Items per page (max 100).
       # @return [Hash] { data: Array<Hash>, meta: { page:, per_page:, total: } }
-      def event_callbacks(id, status: nil, topic: nil, payment_id: nil, since: nil,
-                          until_time: nil, sort: nil, page: nil, per_page: nil)
-        query = build_query(status: status, topic: topic, payment_id: payment_id, since: since,
-                            until: until_time, sort: sort, page: page, per_page: per_page)
+      def event_callbacks(id, status: nil, topic: nil, payment_id: nil, response_code: nil,
+                          since: nil, until_time: nil, sort: nil, page: nil, per_page: nil)
+        query = build_query(status: status, topic: topic, payment_id: payment_id,
+                            response_code: response_code, since: since, until: until_time,
+                            sort: sort, page: page, per_page: per_page)
         http.get_list("/webhooks/#{id}/event_callbacks#{query}")
       end
 
+      # Re-deliver one recorded delivery's exact payload
+      # (POST /webhooks/:id/event_callbacks/:callback_id/redeliver).
+      #
+      # The recovery lever for events lost while the circuit breaker was open: the
+      # gateway stores each delivery's payload and replays THAT payload verbatim — the
+      # same embedded event id, so a receiver that already processed it deduplicates —
+      # under a fresh timestamped signature.
+      #
+      # Delivery is ASYNC (the standard dispatcher: same SSRF checks, retries and circuit
+      # accounting), and the dispatcher drops a delivery for a webhook that is not active.
+      # So re-activate the webhook FIRST — {enable} if it was disabled, {reset_circuit} if
+      # the breaker opened — or the 202 below is answered and the replay silently dropped.
+      #
+      # A callback id that is malformed, unknown, belongs to another webhook, or was
+      # recorded before payloads were stored all answer 404.
+      #
+      # @param id [String] Webhook UUID.
+      # @param callback_id [String] The event callback's UUID (from {event_callbacks}).
+      # @return [Hash] `{ status: "queued" }` (HTTP 202).
+      def redeliver(id, callback_id)
+        http.post("/webhooks/#{id}/event_callbacks/#{callback_id}/redeliver", {})
+      end
+
       # Delete a webhook. Returns HTTP 204.
       # @param id [String] Webhook UUID.
       # @return [nil]

data/lib/rail0/stablecoins.rb

@@ -78,13 +78,50 @@ module Rail0
           "cUSD" => StablecoinInfo.new(address: "0x765DE816845861e75A25fCA122bb6898B8B1282a", decimals: 18, eip3009: true, eip2612: false),
           "cEUR" => StablecoinInfo.new(address: "0xD8763CBa276a3738E6DE85b4b3bF5FDed6D6cA73", decimals: 18, eip3009: true, eip2612: false)
         }
+      ),
+      # ── Testnets ───────────────────────────────────────────────────────────
+      # Every address below was read off its own chain, and the token lists are
+      # the immutable acceptedTokens() allowlists of the RAIL0 deployments there
+      # — which is what a payment on that chain can actually use.
+      "arc-testnet" => ChainStablecoins.new(
+        chain_id: 5042002,
+        tokens: {
+          "USDC" => StablecoinInfo.new(address: "0x3600000000000000000000000000000000000000", decimals: 6, eip3009: true, eip2612: true),
+          "EURC" => StablecoinInfo.new(address: "0x89B50855Aa3bE2F677cD6303Cec089B5F319D72a", decimals: 6, eip3009: true, eip2612: true)
+        }
+      ),
+      # Celo Sepolia is 11142220. The rail0-go registry carried 44787 here, which is
+      # ALFAJORES — a different, now-retired network — alongside a USDC address with
+      # no code on this chain. Corrected there in the same change; do not "restore" it.
+      "celo-sepolia" => ChainStablecoins.new(
+        chain_id: 11142220,
+        tokens: {
+          "USDC" => StablecoinInfo.new(address: "0x01C5C0122039549AD1493B8220cABEdD739BC44E", decimals: 6, eip3009: true, eip2612: true),
+          "USD₮" => StablecoinInfo.new(address: "0xd077A400968890Eacc75cdc901F0356c943e4fDb", decimals: 6, eip3009: true, eip2612: true)
+        }
+      ),
+      # PYUSD is the first non-Circle token served, and the reason this chain is
+      # served at all — it is issued nowhere else.
+      #
+      # Signing against PYUSD directly: its EIP-712 domain name is "PayPal USD", not
+      # the symbol, and its version is "1", which version() does not expose (it
+      # reverts). Through a RAIL0 payment this never bites — the domain comes down in
+      # the gateway's signing_payload — but building the domain by hand from the
+      # symbol yields a signature the token rejects.
+      "ethereum-sepolia" => ChainStablecoins.new(
+        chain_id: 11155111,
+        tokens: {
+          "USDC"  => StablecoinInfo.new(address: "0x1c7D4B196Cb0C7B01d743Fbc6116a902379C7238", decimals: 6, eip3009: true, eip2612: true),
+          "PYUSD" => StablecoinInfo.new(address: "0xCaC524BcA292aaade2DF8A05cC58F0a65B1B3bB9", decimals: 6, eip3009: true, eip2612: true)
+        }
       )
     }.freeze
 
     # Returns the registry entry for a chain, or +nil+ if the chain is unknown.
     #
     # Supported chain names: "ethereum", "base", "polygon", "arbitrumOne",
-    # "optimism", "avalanche", "celo".
+    # "optimism", "avalanche", "celo", "arc-testnet", "celo-sepolia",
+    # "ethereum-sepolia".
     #
     # @param chain [String]
     # @return [ChainStablecoins, nil]

data/lib/rail0/types.rb

@@ -46,36 +46,43 @@ module Rail0
       keyword_init: true
     )
 
-    # Error envelope. Every error this API returns carries `code` (stable and machine-readable — the
-    # only field to branch on), `title` (a short label) and `detail` (one or two sentences fit to show a
-    # user verbatim). The wording comes from the gateway's error catalogue, so the same condition always
-    # reads the same way wherever it surfaces. `status` and `message` are the pre-code/title/detail
-    # names, derived from the same entry and kept for existing clients: `status` carries the family a
-    # client used to switch on (e.g. `forbidden`, `invalid_state`) where `code` is narrower, and
-    # `message` equals `detail`. Context fields may also be present (`resource`, `param`, `chain_id`,
-    # `token`, `payee`, `errors`).
+    # The error envelope: exactly code (stable, the only field to branch on), title (short label) and
+    # detail (a sentence a UI can print verbatim). The legacy status/message/error aliases were removed
+    # in #252.
     ApiErrorBody = Struct.new(
-      :code,     # String
-      :title,    # String
-      :detail,   # String
-      :status,   # String — Legacy: the error family, or the code itself when there is no wider family.
-      :message,  # String — Legacy alias of `detail`.
+      :code,    # String
+      :title,   # String
+      :detail,  # String
       keyword_init: true
     )
 
-    # Gateway liveness/readiness. Only the database gates the HTTP code (200 healthy, 503 when the DB is
-    # unreachable); Sidekiq is reported but never flips the code, since the API still serves synchronous
-    # requests when workers are down. `status` is the global signal: `ok` (all good), `degraded` (DB ok
-    # but Sidekiq not ok), `error` (DB down — the only 503).
+    # Gateway liveness/readiness — public and token-blind: one body for every caller, and every field is
+    # public by nature (the versions are on-chain / on the root descriptor; the counts are derivable
+    # from the public catalog reads). Only the database gates the HTTP code (200 healthy, 503 when the
+    # DB is unreachable); the Sidekiq worker fleet never flips the code, since the API still serves
+    # synchronous requests when workers are down. `status` is the global signal: `ok` (all good),
+    # `degraded` (DB ok but the worker fleet not ok), `error` (DB down — the only 503). The fleet
+    # FIGURES (queue depth, worker count, Redis reachability) are operational internals and live on the
+    # operator-only GET /admin/health.
     Health = Struct.new(
       :status,            # String
+      :db,                # String
+      :timestamp,         # String
       :api_version,       # String
       :contract_version,  # String
-      :db,                # String
-      :sidekiq,           # Hash — Worker fleet health (does not gate liveness).
       :active_chains,     # Integer
       :active_contracts,  # Integer
-      :timestamp,         # String
+      keyword_init: true
+    )
+
+    # Operator diagnostics for GET /admin/health: one verdict plus a named check per standing failure
+    # condition, always 200 (a degraded system is the content, not an error — this is not a liveness
+    # probe). Every figure is computed on request from state the gateway already keeps; nothing here is
+    # a counter anyone increments.
+    AdminHealth = Struct.new(
+      :status,     # String — The worst of the checks. Exists so "is anything wrong" can be read without knowing which checks there are, nor which will be added later.
+      :checks,     # Hash
+      :timestamp,  # String
       keyword_init: true
     )
 
@@ -89,7 +96,9 @@ module Rail0
     # Issued after a successful SIWE verification. SIWE alone proves control of the address, so a token
     # is issued even when the address is not registered to any account; in that case `account_id` and
     # `name` are null (an account-less session, e.g. a buyer). Clients that require an account must
-    # treat a null `account_id` as not-allowed.
+    # treat a null `account_id` as not-allowed. A session whose account holds the operator grant
+    # additionally carries `admin: true` (the Session::Admin variant); a standard or account-less
+    # session has no admin/role field at all.
     Session = Struct.new(
       :token,       # String — JWT bearer token.
       :address,     # String — Resolved wallet address.
@@ -99,20 +108,31 @@ module Rail0
       keyword_init: true
     )
 
+    # The RAIL0 deployment a NEW payment on this chain is opened against — what escrows the payer's
+    # funds, and which version of it. Nothing here is a disclosure: the address is on-chain, every
+    # payment response already carries it as `rail0_contract`, and the explorer shows its verified
+    # source. It is published so a client does not carry its own address-per-chain table and go quietly
+    # stale on the next rollout. Null only for a chain with no deployment, which cannot appear in this
+    # listing anyway. The operator's bookkeeping (start_block, active/archived) stays on
+    # /admin/contracts: it describes how this gateway and its indexer are run, not what a payer is
+    # signing into.
+    ChainContract = Struct.new(
+      :address,      # String
+      :version,      # String — Semver of the deployed contract. Every active deployment agrees on the one the gateway targets.
+      :deployed_at,  # String
+      keyword_init: true
+    )
+
     # Public blockchain view.
-    #
-    # required_confirmations and finality_tag together say how long a payer waits. Read
-    # the PAIR, not the number: where a chain serves a finality tag the gateway gates on
-    # that tag, and the count is the fallback for chains serving none — so quoting the
-    # count on a tagged chain names a wait nobody applies.
     Blockchain = Struct.new(
-      :chain_id,               # Integer
-      :name,                   # String
-      :native_symbol,          # String
-      :network_type,           # String
-      :explorer_url,           # String
-      :required_confirmations, # Integer
-      :finality_tag,           # String, nil where the chain serves no tag
+      :chain_id,                # Integer
+      :name,                    # String
+      :native_symbol,           # String
+      :network_type,            # String
+      :explorer_url,            # String
+      :required_confirmations,  # Integer — Confirmations this gateway waits for before treating a transaction as settled. The FALLBACK rule: where the chain serves a finality tag (see finality_tag) that tag governs instead, so a client showing this number on such a chain is describing a rule that is not in force.
+      :finality_tag,            # String — The block tag the chain calls settled (`safe`, `finalized`), when it serves one — and what the gateway actually gates on. Null where the chain serves none, in which case required_confirmations is counted.
+      :contract,                # ChainContract
       keyword_init: true
     )
 
@@ -150,9 +170,10 @@ module Rail0
     # A wallet's token holding as nested under its wallet (GET /accounts/:id/wallets): the token plus
     # this wallet's per-token flags, without re-nesting the wallet.
     WalletTokenHolding = Struct.new(
-      :token,    # Token
-      :active,   # Boolean
-      :default,  # Boolean
+      :token_id,  # String — The token's UUID — the handle for PATCH/DELETE /accounts/{account_id}/wallets/{id}/tokens/{token_id}.
+      :token,     # Token
+      :active,    # Boolean
+      :default,   # Boolean
       keyword_init: true
     )
 
@@ -167,28 +188,25 @@ module Rail0
       keyword_init: true
     )
 
-    # Base persisted payment fields.
+    # Base persisted payment fields, plus the `chain_id` of the payment's deployment.
     Payment = Struct.new(
       :id,                    # String
       :contract_id,           # String
-      :chain_id,              # Integer — EVM chain id of the deployment. On list rows too: `amount` is
-      #                         base units, and the token's decimals resolve from `token` PLUS its chain.
+      :chain_id,              # Integer — EVM chain id of the payment's deployment. Present on the list view too: `amount` is in base units, and the token's `decimals` can only be resolved from `token` together with its chain.
       :rail0_id,              # String — Protocol-level identifier (66-char hex).
-      :status,                # String
+      :status,                # String — Lifecycle state. Deliberately a HAPPY-PATH label, not a ledger: a partial operation does NOT move it, so a payment captured 100 and refunded 40 still reads `captured`, and a full refund that leaves uncaptured escrow does too. `capturable_amount` / `refundable_amount` are the authoritative residuals — reconcile on those, not on this. `partially_refunded` is retained for historical rows only and is no longer produced.
       :mode,                  # String
       :amount,                # String
       :capturable_amount,     # String — Mirrors on-chain capturableAmount (escrow still held); base units.
       :refundable_amount,     # String — Mirrors on-chain refundableAmount (held by payee, still refundable); base units.
-      # The window after a PARTIAL capture where neither void nor release can return the
-      # buyer's remaining escrow — the answer to "why did both just refuse?".
-      :escrow_stranded,       # Boolean
-      :escrow_returnable_at,  # String, nil — ISO-8601 end of that window; nil outside it.
       :config_hash,           # String
       :payer,                 # String
       :payee,                 # String
       :token,                 # String
       :authorization_expiry,  # Integer
       :refund_expiry,         # Integer
+      :escrow_stranded,       # Boolean — True exactly inside the stranded-escrow window (#233): a partial capture has permanently ruled void out, and release only opens at authorization_expiry — so no verb can return the buyer's uncaptured escrow until then. Mirrors RAIL0.sol; the gateway names the window, it cannot shorten it.
+      :escrow_returnable_at,  # String — When the stranded escrow becomes returnable (release opens) — the authorization expiry as ISO-8601. Null whenever nothing is stranded, so presence alone is the signal.
       :disputed,              # Boolean — True while an open dispute exists.
       :last_error_code,       # Decoded reason of the last failed on-chain attempt; null once the payment makes forward progress. Non-null means the latest attempt failed.
       :last_error_message,    # Human-readable form of last_error_code.
@@ -218,15 +236,16 @@ module Rail0
     Transaction = Struct.new(
       :id,                    # String
       :payment_id,            # String
-      :operation,             # String
+      :operation,             # String — Which on-chain call this row attempts. A SUPERSET of the `{operation}` path enum: `dispute` and `close_dispute` have their own hand-written routes rather than living under the generic namespace, but they mint transaction rows like any other operation, so a generated client must be able to represent them.
       :status,                # String
+      :redrivable,            # Boolean — True when this transaction's broadcast can be re-enqueued: it is `pending` and the gateway holds its signed transaction, i.e. a send that was prepared and signed but never reached the chain. The same predicate `POST /payments/{id}/transactions/{transaction_id}/redrive` guards on, so a client can offer the action exactly when it will succeed instead of on a 422. False on a `pending` row that holds no signed transaction - there the next step is submitting the signature, not a redrive.
       :error_code,            # Decoded failure code, null unless `status` is "failed". Same catalogue as an error body's `code`: a RAIL0 custom error (`not_payee`), a token-level revert (`insufficient_token_balance`, `invalid_token_signature`, `authorization_already_used`), a Solidity panic, or a rejection that stopped the broadcast before the chain saw it (`insufficient_gas_funds`, `nonce_too_low`).
       :error_title,           # String — Short label for `error_code`; null unless failed.
       :error_detail,          # String — Sentence explaining the failure; null unless failed. Carries the chain's own words when the revert was not one the gateway recognises.
-      :error_message,         # Legacy alias of `error_detail`.
       :unsigned_transaction,
       :transaction_hash,
-      :amount,
+      :sender,                # The address that SIGNED the submitted transaction, recovered from the signature by the gateway at submit — a fact, not a client claim. Null where the gateway held no signature to recover from (a report-by-hash submit, where the wallet broadcast it itself) or where nothing has been submitted yet. This is what makes `release` gas attributable: that operation is payer-OR-payee, so whose cost it is depends on who signed.
+      :amount,                # Amount in token BASE units. On capture and refund it is the amount the caller asked for. On void and release it is PROVISIONAL — those operations carry no amount and move the whole uncaptured escrow, so this is the capturable residual as of prepare, re-sealed with the exact on-chain amount when the indexer confirms.
       :block_number,
       :gas_used,              # Gas units used, mirrored from the indexer on confirm.
       :gas_limit,             # Gas limit, mirrored from the indexer on confirm.
@@ -241,11 +260,41 @@ module Rail0
       keyword_init: true
     )
 
+    # Full RAIL0 deployment row (admin surfaces only). Read alongside AdminBlockchain: a chain with no
+    # row here cannot take a payment, which is what keeps it out of service.
+    AdminContract = Struct.new(
+      :id,             # String
+      :blockchain_id,  # String
+      :address,        # String
+      :version,        # String — Semver, and every ACTIVE deployment must agree on the one the code targets.
+      :deployed_at,    # String
+      :start_block,    # Where the indexer starts. Null means the deployment block.
+      :active,         # Boolean — The single deployment new payments are opened against, at most one per chain.
+      :archived,       # Boolean — Always false here: the listing excludes archived deployments.
+      :archived_at,
+      :created_at,     # String
+      :updated_at,     # String
+      keyword_init: true
+    )
+
+    # The account's own profile as the holder reads it (GET) and as a PATCH returns it — id, name,
+    # email, timestamps. Deliberately no admin/role field: the operator grant lives in a separate table,
+    # so a standard account's profile carries no trace of that axis. An ADMIN reading any account gets
+    # the whole record plus `admin` instead, which is a different shape and not this one.
+    Account = Struct.new(
+      :id,          # String
+      :name,        # String
+      :email,
+      :created_at,  # String
+      :updated_at,  # String
+      keyword_init: true
+    )
+
     Webhook = Struct.new(
       :id,                     # String
       :name,                   # String
       :callback_url,           # String
-      :topics,                 # Array<WebhookTopic> — every event this subscription delivers
+      :topics,                 # Array — Every event this subscription delivers. The delivery itself names the one that fired, in X-Rail0-Topic.
       :active,                 # Boolean
       :circuit_state,          # String
       :circuit_failure_count,  # Integer
@@ -272,9 +321,10 @@ module Rail0
     # Sweeper view of a stale submitted transaction.
     SyncTransaction = Struct.new(
       :transaction_hash,  # String
-      :operation,         # String
+      :operation,         # String — Same vocabulary as `Transaction.operation` — dispute rows go stale too.
       :payment_id,        # String — Protocol-level rail0_id.
       :chain_id,          # Integer
+      :contract_address,  # String — Address (lowercase) of the RAIL0 deployment the payment is bound to, archived versions included. The sweeper accepts a receipt's event only when this contract emitted it.
       keyword_init: true
     )
 
@@ -283,8 +333,7 @@ module Rail0
       :chain_id,                # Integer
       :start_block,             # Integer
       :required_confirmations,  # Integer — Fallback burial depth, used where the chain serves no finality tag.
-      :finality_tag,            # String — Which block the chain calls settled ("safe", "finalized" or
-      #                           "depth"); the indexer gates every notify on it.
+      :finality_tag,            # String — Which block the chain calls settled; the indexer gates every notify on it.
       :explorer_url,            # Block explorer base URL; null when the chain has none.
       :network_type,            # String — "testnet" or "mainnet"; selects which chains a deployment indexes.
       :rpc_urls,                # Array — Ordered list of public RPC endpoints tried in turn (serial fallback).

data/lib/rail0/version.rb

@@ -5,5 +5,5 @@ module Rail0
   # consumed by path from a sibling checkout, where the number bought nothing: no registry
   # ever served a 1.x, no tag was ever cut, and the one consumer resolves the working tree.
   # Publishing from 1.2.0 would have implied two releases nobody can install.
-  VERSION = "1.0.0"
+  VERSION = "1.2.0"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: rail0-sdk
 version: !ruby/object:Gem::Version
-  version: 1.0.0
+  version: 1.2.0
 platform: ruby
 authors:
 - Commerce Layer
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2026-09-21 00:00:00.000000000 Z
+date: 2026-09-29 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: logger
@@ -84,7 +84,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.5.11
+rubygems_version: 3.5.22
 signing_key:
 specification_version: 4
 summary: Ruby SDK for the RAIL0 stablecoin payment protocol