why1 reason
data_leakpayment_card
payment_note carries a payment card number (41************11), which would be written to a permanent public record
what it was decided fromfingerprints
- rule compiled from it
- 0600a90a94e6aeaf5ce9813c02da3a5c4b245d728727825d9bf7ceb5bbb55990
- request
- 112a801252ffb976d22b651c68058f30fdfca6003fa8df70570d3852baa3db33
- transaction
- b72984d260b6206e0e0e9c6c3b41da712238909364156d9c04e86d62d7f58713computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 821
the chainentry 821
- sealed to the entry before
- b5d2865a5b4ef48c1d366933c2e397293a97ced7902b03ddac7df1fed47b0f54
- this leaf
- fc0cc9d3e26f8f122ff6ec1e883784f08f66632422a6eb9b045d32aaa04a6989
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- sBf6/x442H+unjnb40DvipdIRxajy7HwSSasN2aLU2DaAwaXrkukZ3+zZRIzqeN209FawfxYTT5vk/GLtjfCAA==