# The portal measures two more steps on a partner's way in

- Date: 2026-10-25
- Type: Non-breaking change
- Surface: Developer portal and CLI
- What you need to do: Nothing.
- Address: https://developers.rivr.io/changelog/2026-10-25-partner-funnel-signed-delivery-and-test-payment

The portal counts the steps a partner organisation takes from the invitation to a first test payment, to measure how long the way in takes: invitation accepted, first sign-in, first key, first webhook endpoint and, new, the first signed delivery to your relay and the first test payment from `rivr trigger --complete`. A delivery counts when it reaches your relay while `rivr listen` is connected, with both Rivr-Signature and a Rivr-Webhook-Id (an id of 1 to 200 characters; the portal does not check its format, since the id is an opaque string). A delivery that arrives while nobody listens, and only waits in the relay's buffer, does not count; the next one while `rivr listen` is connected does. The relay has no signing secret and cannot verify the signature, so the step means that the delivery arrived signed with an id at a connected listener, not that it was verified. A test payment counts when `rivr trigger --complete` takes the order to Completed with a card or Swish, or to Pending with an invoice; a payment you declined on purpose does not count. For each organisation the portal keeps only the organisation id, the name of the step and the time of the first one: no person, no order, no body and no key. Beyond that it remembers, in memory only and as a hash, which organisation a relay address belongs to, to know whose delivery it is. Only partner organisations in the sandbox are counted, not Rivr's own staff and not a clinic's organisation. What the portal, the relay and the CLI answer is unchanged.