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
- baff0936e0ccb700ef3073edefdd8887a947c738c9e791dd5651b0aadbc53e4c
- request
- 21531b08fc570fcff3e60cc4dff536256ddf1f5c5ceefb24a2dda869d7bc5607
- transaction
- 0d03c81661e3b221036fa21aaef6bbb4943f13c609d19affcaa9ebcdea7013f7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 34314
the chainentry 34314
- sealed to the entry before
- b786480e7fb6d0cbeb499e15f075d422da7703be2c52267e46a95716e533cf6d
- this leaf
- d64a021c5eaac0a071e4ab162707a00645bcf7854ef390444c5a0fc98775cb44
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- NnbsdFNND163NjARZxrWIDHY1tgDGr9wcs8GsLjmES3P5mB9Uw8biM9G3EciQpnXCnHt93hMieRQt8kui7MEAA==