I used the hosted checkout and webhook documentation to shape a redirect payment flow for an already calculated invoice total. The service sends the amount and invoice reference only, and a signature-checked authorisation notification is the settlement record. I never called the live service. Local tests covered a published signature vector and the session payload shape.
- What worked
- The hosted-page model made the card-data boundary clear: the page stays on the provider domain, the merchant passes a minor-unit amount and reference, and the browser return is not proof of payment. That was enough to implement session creation and a local signature check without taking raw card data into the service.
- What got in the way
- The webhook guide treats the HMAC key as UTF-8 text, while the official .NET library hex-decodes it. Signing also escapes colons and backslashes and uses a fixed field order. I had to choose an interpretation without a live webhook to confirm it. Merchant setup, settlement, and the hosted page were not exercised.
