manza 0.3.0 → 1.2.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 80076371c65341ec2d0505fee01860048e6198a878249315cda749dd66a848e1
-  data.tar.gz: 489435e29915da758541243d8a02af6f94c8ee6cf5c0322341495e89b84eb9b7
+  metadata.gz: 23d95fcba1fba943b2dd02913102b71a982ad3548745a5a249245ab2ff120211
+  data.tar.gz: 38790ad40aa6bb4c3183f5114eee891e473bff53cbfcb1b2810b0ce986ba9b7e
 SHA512:
-  metadata.gz: af686049cde39a906d1991c3bdf76b1165963c7a759573dc1f60b60ec1f309c822bb44821eedb4691cdca0fe6db0414662387aec7342f07ab45ddf1c2695bb40
-  data.tar.gz: 720050593b2e7399068b20345d99355cd4ee11547f5e335199e28e6c4b5f03039f9472cbe73b1160b8f5e51ba7ceaf7d584dc89fa41d63e75656a13b4bbac5f7
+  metadata.gz: ee8d889d2ec4437866067a0806ae30d381f4efdb3a6548dd79fa9223dee1c831b890dfef7f5ee0c3068147af6acf4ad23ffaec78967b5f7776c05ceb7e51f299
+  data.tar.gz: 28f2074be599fe6edced2ca521b636797cd066f49d40a0a9e5dc22b8705df6884757763fd51420ee8be13a36d33b54b83f67598ed0f4d6de940843328da873df

data/CHANGELOG.md

@@ -7,6 +7,58 @@ This project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.htm
 
 ## [Unreleased]
 
+## [1.2.0]
+
+1.1.0 was never published: its changes (the webhook verifier and the
+example) ship here.
+
+### Added
+
+- `manza.transfer_authorizer.get` (`GET /api/transfer_authorizer`): the
+  enrolled authorizer's `status`, `suspension_reason`, limits,
+  `daily_authorized_total`, `secret_expires_at` and `webhook_endpoint_id`.
+  Raises `Manza::NotFoundError` when none is enrolled.
+- Documented the new pass-through fields: a draft's `authorization` carries
+  `refusal_reason` (status `refused` when it went to the approvers at
+  create time), bank accounts carry `trusted`, and the challenge webhook's
+  `payment.payee_trusted` says whether the payee was trusted already.
+- `examples/transfer_authorizer/`: `preflight.rb` checks every setup step
+  and prints the fix; `create_transfer.rb` prints the authorization status
+  and refusal reason in words; the authorizer logs a new payee, declines it
+  with `ALLOW_NEW_PAYEES=false`, and retries 409 `authorization_busy`.
+- README: setup step 6 is "Approve transfers to new payees" (or trust each
+  payee), step 7 the preflight.
+- Cassettes re-recorded against `ma.manza.dev`, with new ones for
+  `transfer_authorizer/get`, a refused draft, a new-payee authorize and the
+  payee trusted afterwards.
+- `Manza::Webhook` verifies incoming webhook deliveries: `verify?` (boolean),
+  `construct_event` (returns the parsed event, raises `Manza::ArgumentError`)
+  and `sign`. Reads `X-Manza-*` headers in any case, the Rack `HTTP_X_MANZA_*`
+  form and the legacy `X-Zazu-*` names; checks the timestamp within 5 minutes
+  (`tolerance: nil` skips it, for local replay only). The spec carries a fixed test vector every SDK
+  reuses.
+- `examples/transfer_authorizer/`: a runnable two-key transfer authorizer
+  (Rack app plus a creator script and a JSON ledger). Not shipped in the gem.
+- README: "Setup, step by step" for machine-authorized transfers.
+
+### Changed (cassettes)
+
+Two existing cassettes match a different request body. An SDK that replays
+`cassettes-v1.2.0` sends these exact bodies:
+
+- `transfer_drafts/create`: `amount` `"10.00"`, the staging per-transfer
+  limit (the old `"150.00"` exceeds it and was refused), and a new `internal_notes`
+  `"[zazu-ruby-fixture] create spec - do not approve"`. The response's
+  `authorization` is a `pending` challenge.
+- `beneficiaries/create`: `company_name` `"Manza Fixture Beneficiary spec"`
+  (staging now accepts only unaccented letters, digits and spaces).
+
+Responses are scrubbed further: account `balance` and transaction
+`account_balance_after` read the synthetic decimal `"1000.0"`, and the
+authorizer's `daily_authorized_total` reads `"0.0"`, in every cassette.
+
+## [1.0.0]
+
 The SDK is renamed from Zazu to Manza and released as `manza` 1.0.0.
 The API surface is otherwise unchanged.
 
@@ -41,6 +93,16 @@ one-time deprecation warning per variable.
 - Fixture and staging env vars for recording are `MANZA_FIXTURE_*` and
   `MANZA_STAGING_*`, with no fallback. Rename them in your `.env`.
 
+## [0.3.1]
+
+Final release under the old `zazu-ruby` name, published from the
+`zazu-legacy` branch.
+
+### Deprecated
+
+- `require "zazu"` prints a deprecation warning, and the gem shows a
+  post-install message pointing to `gem "manza"`.
+
 ## [0.3.0]
 
 ### Added

data/README.md

@@ -82,7 +82,7 @@ manza.checkout_sessions.get("cs_...")
 manza.beneficiaries.list
 manza.beneficiaries.create(beneficiary_type: "business", company_name: "Acme Supplies", email: "ap@acme.com")
 manza.beneficiaries.list_external_accounts("01a0...")
-manza.beneficiaries.get_external_account("01a0...", "01a1...")
+manza.beneficiaries.get_external_account("01a0...", "01a1...")  # "trusted": true once a trusted payee
 manza.beneficiaries.create_external_account("01a0...", account_number: "007780...", name: "Main account")
 
 manza.payee_trust_requests.create(external_account_ids: ["01a1..."])
@@ -94,9 +94,11 @@ manza.transfer_drafts.create(
   amount: "2500.00",
   client_reference: "po_1042" # unique per entity; a duplicate raises Manza::ConflictError
 )
-manza.transfer_drafts.get("01a3...")
+manza.transfer_drafts.get("01a3...")            # authorization: status, refusal_reason
 manza.transfer_drafts.decline("01a3...", authorization_id: "01a4...", reason: "Not ours")
 
+manza.transfer_authorizer.get  # status, suspension_reason, limits, daily_authorized_total; NotFoundError: none enrolled
+
 manza.webhook_endpoints.list
 manza.webhook_endpoints.create(
   url: "https://example.com/webhooks/manza",
@@ -110,7 +112,47 @@ manza.webhook_endpoints.disable("01a0...")
 
 ## Machine-authorized transfers
 
-A draft inside your entity's authorization envelope (trusted payee, within limits) is sent to your enrolled authorizer endpoint as a `payment.authorization_requested` webhook carrying an `authorization.id` and a one-time `nonce`. Sign the draft from **your own record** of it with the endpoint's signing secret, and authorize it with a **different API key** from the one that created it (the creating key gets 403 `same_key_forbidden`):
+A draft inside your entity's authorization envelope (trusted payee, or a new one when you allow it, within limits) is sent to your enrolled authorizer endpoint as a `payment.authorization_requested` webhook carrying an `authorization.id` and a one-time `nonce`. Your system checks it against its own ledger, signs it and authorizes it with a **different API key** from the one that created it. [`examples/transfer_authorizer/`](examples/transfer_authorizer/) runs the whole flow.
+
+### Setup, step by step
+
+1. **Feature flags.** Ask support to enable API transfers and transfer authorization (`release_api_webhook_authorization`) on your workspace.
+2. **Two API keys.** Key A creates drafts (`transfers:write`; `beneficiaries:request_trust` for step 6; `entity:read`, `accounts:read`, `webhook_endpoints:read` and `beneficiaries:read` for the preflight in step 7). Key B answers the challenges (`transfers:authorize`). The creating key is always refused with 403 `same_key_forbidden`, so keep key B and the signing secret on the system that holds your ledger. Bind key B to an IP allowlist: authorizing from a key without one is refused with 403 `unrestricted_api_key`. Bind key A to one too if you allow new payees (step 6): a draft to a new payee from a key without an allowlist goes to your approvers (`unrestricted_api_key`).
+3. **A stable public URL.** Your authorizer needs an HTTPS URL that never changes: an enrolled endpoint's URL is locked. Use a reserved ngrok domain (`ngrok http --url=your-name.ngrok.app 4599`) or a named Cloudflare tunnel (see [The authorizer tunnel](#the-authorizer-tunnel)). Never a free ngrok URL: it changes on every restart.
+4. **Create the webhook endpoint** at that URL:
+
+   ```ruby
+   manza.webhook_endpoints.create(url: "https://your-name.ngrok.app/", events: ["transfer.executed"])
+   ```
+
+5. **Enrol it in the app**: Settings → Developer → Transfer approval. Pick the endpoint, the currency and both limits, confirm with your two-factor code, and copy the signing secret: it is shown once.
+6. **Allow new payees, or trust each payee.** Turn on *Approve transfers to new payees* at enrolment (or later, same page, with your two-factor code) and set the *Limit per transfer to a new payee*. Your authorizer may then approve a transfer to bank details your workspace never trusted, up to that limit, and its signature trusts them: the webhook's `payment.payee_trusted` is `false` for such a transfer. Bank details whose trust was revoked, or that were edited after trusting, still go to your approvers. Without the option, an approver marks the beneficiary's bank account as trusted from the Beneficiaries list, or you ask them to:
+
+   ```ruby
+   manza.payee_trust_requests.create(external_account_ids: ["01a1..."])
+   ```
+
+   `trusted` on `manza.beneficiaries.get_external_account` says which it is. The API does not show whether the option is on.
+7. **Run the preflight, then the example** (from `examples/transfer_authorizer/`, after `bundle install` and filling in `.env`): `bundle exec ruby preflight.rb` checks what the API shows of steps 1–6 and prints a fix for each that fails. What it cannot see, check by hand: that key B is bound to an IP allowlist, and, for a payee not trusted yet, that *Approve transfers to new payees* is on and key A is bound to an IP allowlist too (it warns, it does not fail). Then `bundle exec rackup -p 4599` in one terminal, `bundle exec ruby create_transfer.rb` in another.
+8. **Troubleshooting**: a draft that goes to your approvers instead has an `authorization` with status `refused` and a `refusal_reason` (`create_transfer.rb` prints it in words); `manza.transfer_authorizer.get` shows a suspension and its `suspension_reason`. An authorize answered 409 `authorization_busy` (a bank-detail edit, trust or trust revocation on the same payee was in flight) is safe to retry. The reasons, and an API error's `type`, are in the [transfer authorization docs](https://ma.manza.finance/docs/api/transfer-authorization).
+
+### Verifying the webhook
+
+Pass the **raw request body**, never re-serialized JSON. `construct_event` reads `X-Manza-Signature` and `X-Manza-Timestamp` (any case, the Rack `HTTP_X_MANZA_*` form, or the legacy `X-Zazu-*` names), checks the signature in constant time and the timestamp within 5 minutes, and returns the parsed event (a Hash). It raises `Manza::ArgumentError` otherwise:
+
+```ruby
+begin
+  event = Manza::Webhook.construct_event(payload: request.body.read, headers: request.env, secret: signing_secret)
+rescue Manza::ArgumentError => e
+  return [401, {}, [e.message]]
+end
+```
+
+`Manza::Webhook.verify?(payload:, signature:, timestamp:, secret:)` returns a boolean instead. Both accept `tolerance: nil` to skip the timestamp check. Use it only to replay a captured delivery in a local tool or test, never on a live endpoint: without the check, anyone holding a captured delivery can replay it.
+
+### Signing the challenge
+
+Sign the draft from **your own record** of it with the endpoint's signing secret:
 
 ```ruby
 input = Manza::TransferAuthorization.signature_input(
@@ -198,13 +240,14 @@ The spec suite is VCR-backed — cassettes live in `spec/fixtures/cassettes/` an
 To re-record cassettes against staging:
 
 ```bash
-cp .env.example .env
+bin/rename-env-vars    # upgrading an existing 0.x .env: ZAZU_* → MANZA_* (backup in .env.bak)
+cp .env.example .env   # fresh setup only — overwrites an existing .env
 # fill in the keys, MANZA_FIXTURE_ACCOUNT_ID and MANZA_FIXTURE_BENEFICIARY_ID
 cloudflared tunnel --config ~/.cloudflared/zazu-sdk-authorizer.yml run zazu-sdk-authorizer   # separate terminal
 bundle exec rake fixtures:record
 ```
 
-Recording executes a real 10.00 MAD transfer on staging (the authorize cassette). The one-time staging setup (keys, authorizer enrolment, trusted payee) is listed at the top of `lib/tasks/fixtures.rake`.
+Recording executes two real 10.00 MAD transfers on staging: the authorize cassette pays the trusted payee, and authorize_new_payee pays a freshly seeded bank account (and trusts it). The one-time staging setup (keys, authorizer enrolment, trusted payee, the new-payee option) is listed at the top of `lib/tasks/fixtures.rake`; AGENTS.md → Staging fixture state keeps it in place.
 
 ### The authorizer tunnel
 
@@ -240,12 +283,26 @@ Check it end to end: with the tunnel running and nothing on port 4599, `curl -X
 
 Cassettes are scrubbed before write — bearer tokens and request IDs are rewritten to placeholders. Even if a real key is in `.env`, the committed cassette never contains it.
 
+## The SDK family
+
+| SDK | Repository | Install |
+|---|---|---|
+| Ruby (reference implementation, records the cassettes) | [getmanza/manza-ruby](https://github.com/getmanza/manza-ruby) (this repo) | `gem "manza"` |
+| TypeScript / JavaScript | [getmanza/manza-ts](https://github.com/getmanza/manza-ts) | `npm install @getmanza/sdk` |
+| Python | [getmanza/manza-python](https://github.com/getmanza/manza-python) | `pip install manza` |
+| Go | [getmanza/manza-go](https://github.com/getmanza/manza-go) | `go get github.com/getmanza/manza-go` |
+| PHP | [getmanza/manza-php](https://github.com/getmanza/manza-php) | `composer require manza/manza-php` |
+| Rust | [getmanza/manza-rust](https://github.com/getmanza/manza-rust) | `cargo add manza` |
+| Crystal | [getmanza/manza-crystal](https://github.com/getmanza/manza-crystal) | shard `manza` (`github: getmanza/manza-crystal`) |
+| Elixir | [getmanza/manza-elixir](https://github.com/getmanza/manza-elixir) | `{:manza, "~> 1.0"}` |
+| CLI | [getmanza/cli](https://github.com/getmanza/cli) | `npm install -g @getzazu/cli` or `brew install getmanza/tap/zazu` |
+
 ## Cassettes for other-language SDKs
 
 Each release of `manza-ruby` publishes the cassette directory as a tarball release asset:
 
 ```
-https://github.com/getmanza/manza-ruby/releases/download/v0.1.0/cassettes-v0.1.0.tar.gz
+https://github.com/getmanza/manza-ruby/releases/download/v1.0.0/cassettes-v1.0.0.tar.gz
 ```
 
 `manza-go`, `manza-python`, etc. pin a specific tag in their cassette fetch script and download the tarball during CI. This guarantees every SDK is tested against the same recorded API interactions, surfacing cross-SDK inconsistencies immediately.

data/lib/manza/client.rb

@@ -91,6 +91,10 @@ module Manza
       @payee_trust_requests ||= Resources::PayeeTrustRequests.new(self)
     end
 
+    def transfer_authorizer
+      @transfer_authorizer ||= Resources::TransferAuthorizer.new(self)
+    end
+
     def transfer_drafts
       @transfer_drafts ||= Resources::TransferDrafts.new(self)
     end

data/lib/manza/resources/beneficiaries.rb

@@ -4,7 +4,10 @@ module Manza
   module Resources
     # Saved transfer recipients. Each beneficiary embeds its bank
     # accounts; the one flagged `default` is used when a transfer names
-    # only the beneficiary_id. There is no update or delete via the API.
+    # only the beneficiary_id. Each bank account carries `trusted`: whether
+    # its bank details are a trusted payee, which machine-authorized
+    # transfers need (or "Approve transfers to new payees" on for details
+    # never trusted). There is no update or delete via the API.
     class Beneficiaries < Base
       # GET /api/beneficiaries
       def list(limit: MAX_PER_PAGE, cursor: nil)

data/lib/manza/resources/transfer_authorizer.rb

@@ -0,0 +1,27 @@
+# frozen_string_literal: true
+
+module Manza
+  module Resources
+    # The entity's enrolled transfer authorizer, read-only. Enrolment,
+    # limits, the "Approve transfers to new payees" option and resume stay
+    # in the app behind a second factor. A singular resource: no list, no id.
+    #
+    #   manza.transfer_authorizer.get.body["status"]  # => "active"
+    class TransferAuthorizer < Base
+      # GET /api/transfer_authorizer
+      #
+      # Any key with `transfers:read`, `transfers:write` or
+      # `transfers:authorize`. Returns `status` (`active` / `suspended`),
+      # `suspension_reason` (`member`, `signature_failures`,
+      # `secret_expired`, `endpoint_disabled`; nil when active),
+      # `currency_code`, `per_transfer_limit`, `daily_limit`,
+      # `daily_authorized_total` (the last 24 hours), `secret_expires_at`,
+      # `webhook_endpoint_id` and `enrolled_at`. It does not show whether
+      # new payees are approved. Raises {Manza::NotFoundError} when no
+      # authorizer is enrolled.
+      def get
+        http_get("api/transfer_authorizer")
+      end
+    end
+  end
+end

data/lib/manza/resources/transfer_drafts.rb

@@ -12,6 +12,31 @@ module Manza
     # representative approves it. Poll {#get} (status: requested →
     # processing → completed / failed) or subscribe to the
     # `transfer.executed` webhook to follow execution.
+    #
+    # A draft's `authorization` says which way it went: `pending` (a
+    # challenge was sent), `authorized`, `declined` (the draft is deleted),
+    # or one of two outcomes that send the draft to the in-app approvers,
+    # each with a `refusal_reason`:
+    #
+    # - `refused`: it did not qualify, at create time (no webhook is sent)
+    #   or again when the challenge was answered: `untrusted_payee`,
+    #   `unrestricted_api_key`, `over_new_payee_limit`,
+    #   `over_transfer_limit`, `over_daily_limit`, `currency_mismatch`,
+    #   `suspended` or `secret_expired`.
+    # - `expired` / `superseded` / `failed`: a challenge was sent and closed
+    #   without an authorize: `expired` (no answer within the hour),
+    #   `stale` (the draft, its payee's bank details or the endpoint changed
+    #   while it was open) or `signature_failed` (five invalid signatures).
+    #   One exception: the in-app approval that finalizes the draft while
+    #   its challenge is open supersedes it (`stale`), and the draft
+    #   executes or is scheduled; the draft's own `status` shows which.
+    #
+    # `authorization` is nil when no authorizer was enrolled.
+    #
+    # With "Approve transfers to new payees" on (enrolment, in the app),
+    # a draft to bank details the entity never trusted is challenged too,
+    # up to the new-payee limit, when the creating key has an IP
+    # allowlist; authorizing it also trusts the payee.
     class TransferDrafts < Base
       # POST /api/transfer_drafts
       #
@@ -36,8 +61,12 @@ module Manza
       # `payment.authorization_requested` webhook; build `signature` with
       # {Manza::TransferAuthorization}. Requires the `transfers:authorize`
       # scope on a key other than the draft's creator (otherwise 403
-      # `same_key_forbidden`). A blank signature is refused locally: the
-      # API counts it as a failed attempt, and five fail the challenge.
+      # `same_key_forbidden`), bound to an IP allowlist (otherwise 403
+      # `unrestricted_api_key`). A 409 {Manza::ConflictError} with `type`
+      # `authorization_busy` means a bank-detail edit, trust or trust
+      # revocation on the payee was in flight: retry. A blank signature
+      # raises {Manza::ArgumentError} and is never sent: the API would count
+      # it as a failed attempt. Five invalid signatures fail the challenge.
       def authorize(id, authorization_id:, signature:)
         raise Manza::ArgumentError, "signature cannot be blank" if signature.to_s.strip.empty?
 
@@ -50,7 +79,8 @@ module Manza
       # POST /api/transfer_drafts/:id/decline
       #
       # Declines the challenge and deletes the draft. Returns the
-      # authorization (`status: "declined"`).
+      # authorization (`status: "declined"`, `declined_at`, and a nil
+      # `refusal_reason`).
       def decline(id, authorization_id:, reason: nil)
         http_post(
           encode_path("api/transfer_drafts", id, "decline"),

data/lib/manza/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Manza
-  VERSION = "0.3.0"
+  VERSION = "1.2.0"
 end

data/lib/manza/webhook.rb

@@ -0,0 +1,100 @@
+# frozen_string_literal: true
+
+require "json"
+require "openssl"
+
+module Manza
+  # Verifies incoming webhook deliveries. Pure functions — no HTTP.
+  #
+  # Every delivery carries `X-Manza-Signature` (hex HMAC-SHA256 of
+  # "<timestamp>.<raw body>" under the endpoint's signing secret) and
+  # `X-Manza-Timestamp` (Unix seconds, fresh on every attempt). The
+  # legacy `X-Zazu-*` names carry the same values.
+  #
+  # Pass the **raw request body**, never re-serialized JSON:
+  #
+  #   event = Manza::Webhook.construct_event(
+  #     payload: request.body.read, headers: request.env, secret: signing_secret
+  #   )
+  #   event["event"] # => "payment.authorization_requested"
+  module Webhook
+    DEFAULT_TOLERANCE = 300 # seconds
+
+    module_function
+
+    # Hex HMAC-SHA256 of "<timestamp>.<payload>". For tests and local tools.
+    def sign(payload:, timestamp:, secret:)
+      OpenSSL::HMAC.hexdigest("SHA256", secret, "#{timestamp}.#{payload}")
+    end
+
+    # true when the signature matches (constant time) and the timestamp is
+    # within `tolerance` seconds of `now`. `tolerance: nil` skips the
+    # timestamp check (for replaying a captured delivery). Never raises on
+    # bad input; returns false.
+    def verify?(payload:, signature:, timestamp:, secret:, tolerance: DEFAULT_TOLERANCE, now: Time.now)
+      signature_matches?(payload, signature, timestamp, secret) && timestamp_fresh?(timestamp, tolerance, now)
+    end
+
+    # Reads X-Manza-Signature / X-Manza-Timestamp from any Hash-like
+    # headers (case-insensitive, X-Zazu-* fallback, Rack HTTP_X_MANZA_*
+    # form too), verifies them, and returns the parsed JSON Hash. Raises
+    # Manza::ArgumentError when a header is missing, the signature does
+    # not match, the timestamp is outside tolerance, or the body is not
+    # a JSON object.
+    def construct_event(payload:, headers:, secret:, tolerance: DEFAULT_TOLERANCE, now: Time.now)
+      normalized = normalize_headers(headers)
+      signature = header(normalized, "signature")
+      timestamp = header(normalized, "timestamp")
+
+      raise Manza::ArgumentError, "invalid webhook signature" unless signature_matches?(payload, signature, timestamp, secret)
+      raise Manza::ArgumentError, "webhook timestamp outside tolerance" unless timestamp_fresh?(timestamp, tolerance, now)
+
+      event =
+        begin
+          JSON.parse(payload)
+        rescue JSON::ParserError
+          raise Manza::ArgumentError, "webhook payload is not JSON"
+        end
+      raise Manza::ArgumentError, "webhook payload is not a JSON object" unless event.is_a?(Hash)
+
+      event
+    end
+
+    def signature_matches?(payload, signature, timestamp, secret)
+      return false unless payload.is_a?(String) && secret.is_a?(String) && !secret.empty?
+      return false unless [signature, timestamp].all? { |v| v.is_a?(String) || v.is_a?(Integer) }
+      return false unless parse_timestamp(timestamp)
+
+      expected = sign(payload: payload, timestamp: timestamp, secret: secret)
+      return false unless expected.bytesize == signature.to_s.bytesize
+
+      OpenSSL.fixed_length_secure_compare(expected, signature.to_s)
+    end
+
+    def timestamp_fresh?(timestamp, tolerance, now)
+      return true if tolerance.nil?
+
+      seconds = parse_timestamp(timestamp)
+      !seconds.nil? && (now.to_i - seconds).abs <= tolerance
+    end
+
+    def parse_timestamp(timestamp)
+      Integer(timestamp.to_s, 10)
+    rescue ::ArgumentError, TypeError
+      nil
+    end
+
+    def normalize_headers(headers)
+      headers.to_h.transform_keys { |name| name.to_s.sub(/\AHTTP_/i, "").tr("_", "-").downcase }
+    end
+
+    def header(normalized, suffix)
+      value = normalized["x-manza-#{suffix}"] || normalized["x-zazu-#{suffix}"]
+      return value.to_s unless value.nil? || value.to_s.empty?
+
+      raise Manza::ArgumentError, "missing X-Manza-#{suffix.capitalize} header"
+    end
+
+    private_class_method :signature_matches?, :timestamp_fresh?, :parse_timestamp, :normalize_headers, :header
+  end
+end

data/lib/manza.rb

@@ -21,6 +21,7 @@ require_relative "manza/errors"
 require_relative "manza/response"
 require_relative "manza/page"
 require_relative "manza/transfer_authorization"
+require_relative "manza/webhook"
 require_relative "manza/resources/base"
 require_relative "manza/resources/accounts"
 require_relative "manza/resources/beneficiaries"
@@ -30,6 +31,7 @@ require_relative "manza/resources/entity"
 require_relative "manza/resources/invoices"
 require_relative "manza/resources/payee_trust_requests"
 require_relative "manza/resources/payment_links"
+require_relative "manza/resources/transfer_authorizer"
 require_relative "manza/resources/transfer_drafts"
 require_relative "manza/resources/webhook_endpoints"
 require_relative "manza/client"

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: manza
 version: !ruby/object:Gem::Version
-  version: 0.3.0
+  version: 1.2.0
 platform: ruby
 authors:
 - Manza
@@ -76,11 +76,13 @@ files:
 - lib/manza/resources/invoices.rb
 - lib/manza/resources/payee_trust_requests.rb
 - lib/manza/resources/payment_links.rb
+- lib/manza/resources/transfer_authorizer.rb
 - lib/manza/resources/transfer_drafts.rb
 - lib/manza/resources/webhook_endpoints.rb
 - lib/manza/response.rb
 - lib/manza/transfer_authorization.rb
 - lib/manza/version.rb
+- lib/manza/webhook.rb
 homepage: https://github.com/getmanza/manza-ruby
 licenses:
 - MIT
@@ -104,7 +106,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 4.0.6
+rubygems_version: 3.6.9
 specification_version: 4
 summary: Ruby SDK for the Manza API
 test_files: []