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
- 71cfab333f5d405eadd7530a4bed630ddc5473c1b0f654b10daa22b44a79627c
- request
- 5c5eabd07701e8d2dfc11f7fed780fc5606c1c3c2858496585397ec4e151d6b4
- transaction
- c2f1deaab94dfdba725df8ea6dca01ca0912b354fde20f7adfe2e5f2914e9fd7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 48565
the chainentry 48565
- sealed to the entry before
- 54fe4ba4a4d7a67025a16518e5d49e0111b8f9de9d29b873036984e6806f1d15
- this leaf
- e464d0f1df1f1847949dbdbc412a0dc36c6b3c70ab6512022a85c52298d281a1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- AmGkdbACGD9xdECthIIXiWWE+JA5ddXWYPpRrXAgTzF0HlTRTLZgc4M/YBqXXUDmeMX3D+B7Zz+rYJnSFpqNDQ==