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
- 43ea3b3626718f5489ec33be4010cc56ca861cd1799bfe8a992a008fe2699d64
- request
- c74eeb1d0871d84b4c1cf07d50f50d387d61e8831126da43f131ffd92b0e0fd9
- transaction
- 36c5278b1cd6278867e0c956b0d71bb94ad3f404b5dc2d30cab4e62912dbc880computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 71619
the chainentry 71619
- sealed to the entry before
- 0c6ef3d186ffb68bd60438f453e8a3002da01051136be68feb28b8be177da5a3
- this leaf
- 9ac191396c853fd232a86e992e8d85679573606175db544a24df36fdcc1e1660
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- cN7g63fvh9BTv3a7T+ZXyH6+X2hxCgpArDMb6kKhCsC5othHJc+eO2Seua/NpW8KPm4hZnUmdUywmthyyuJsCA==