FixedBackend
Signature headers from Creem, Paddle, Gumroad and Patreon now reach verification
PayGlue stores an incoming webhook first and verifies it a moment later from the queue. The queue kept only a fixed list of headers, and that list still dated from the first three providers. For Creem this meant every delivery to a publication failed verification with a missing signature header while the provider saw a normal 200. Fixed on 13 September. The list now carries every header an adapter reads, and a test compares it against the adapter code so a future provider cannot ship without its header. If you connected Creem before this date and a purchase did not unlock a reader, the event is in your event log with a failed status. Replay it, or reply to any of our mails and we do it for you.
- Creem deliveries to publications failed verification before 13 September, the provider saw a 200
- The header list is now checked against the adapters in CI
- Failed events from before the fix can be replayed from the event log
