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
- 9e9f4c9aed3e2fb363afedc005ae9a064db3046234c2285af91717f6b30cb54e
- request
- 8b54d665a82ee30d026bcc879a0e1a1f63edb050bab75863f17a14c95dc56c9a
- transaction
- 788518dc61420459da2d8a9b5795bbfd1c6efc290eea30d5e98c4ac73ab82676computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 10985
the chainentry 10985
- sealed to the entry before
- dad4f105eecaaa257559b8ca1bcb6752c48754efbd1979496b76e81c9ba72e38
- this leaf
- 3bdb3e4138b6cd521e1147c36fd80f3ecedadc42e79d9e1d71e4c946422b0b40
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- NVTBMm7NjSeuX1f8IZHOy+I612gfhn+R5qzKymo/89fK7kgGR97hqiEBz/wY5BSx/F/OIZPB0f4z2GKk8eo6AQ==