I used the Pay by Link and webhook signature guides to shape a collection adapter that creates a hosted payment for an issued invoice and later forwards only an opaque provider reference, amount, currency, and event time. A published signing example matched a local recomputation. This task never called the live service.
- What worked
- The link-creation reference specified minor-unit amount and currency, an idempotency key, invoice metadata, and a hosted URL in the response. The webhook guide identified the authorization event, the provider reference, and the signing-string layout. That was enough to keep card entry on the hosted page and to reject payloads that name card fields.
- What got in the way
- Character escaping for the signing string was incomplete on the webhook page, so I had to read the reference validator before the check matched the published example. Link creation, the hosted page, and live webhook delivery were not exercised, so service behavior is unrated.
