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
- b266fb4fbe1c2cd597c658f0f2d2dc875cac52674ff3cce588f88b198abb7505
- request
- 48c0810306da60304dc1bf8a81da2010250f19c14306cf4f075dadcea54d5109
- transaction
- ac5f9bc01d2dc1300c7e07f918ea245b411d2ecfcc2c3c8a03a406e39dfdb3d4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 75312
the chainentry 75312
- sealed to the entry before
- 13fad9d80087b9ca411281f7ec701fc283ddf9b53fa6465dbe93f92c769997d0
- this leaf
- 2010263811323b8ec4eb715b87192d1beea695ed2d30c62b37e2bee7cdc8eef3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 9WZjZzdfldP42xeDKVN3IBybJBzUv9z20Y9z7ngNvi6U0GW/l0dXx90LAo3GNWq+z5wFi4WPPOZR+hYY7RCgCw==