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
- f23df9cc3bfe3323f61da87326d3f2bdd6685f7081994ad20918c2f77ea1475d
- request
- 3a0da76836e4683331f3c763ed03b740db08cfd6d8cc2306485348d7c6e293ca
- transaction
- cb44a220db9c276624a7d5de9fd92f3b662fee30603cde52f0a96c2d85dded6fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 35383
the chainentry 35383
- sealed to the entry before
- 7c7d2f20fbaa0f7f76aac66cc86e1d5b9708c9f388b33bd2c6f681715a465868
- this leaf
- 10e00a9625d36bbdeef09c07ecd371dc9452ccea0fd978c0b1e4ecacfc586383
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- CQIfB8royqWWEH1FZP0xN2rbh+dgBgZHa757f/ROCHN5Ojfx0q9ux43ON1nwPkoe2pIMiGIWkv/04+4O3mxdCw==