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
- 29bc4da5657d152bedac57fc120e250f3b0f60404307397d67d4a07ceb94ceff
- request
- 53b07f73533266cd100888e522ddb9eef6cd599037e20da97bb2324c10fa93df
- transaction
- 033a24d1ddaa2dcc7488e1643682533ff3a54d51da3ca52737ebacfd5121dbbfcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 17729
the chainentry 17729
- sealed to the entry before
- dd44a9aa480999a0d2673f195c7a5b8680033ec97359a22df88e3524d3661fc0
- this leaf
- 0a0c5600be0b3f75a94df22bdcff82dead86ef7b829e7c644a45201af4aaa968
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- eJu9+z9fgWJ3ItMb28Yx4BBW7jU2UqcthZ79AKF3UNBUsZpccGEBHZq4SaoNuf/LPGNaDBE/VajxAO+wFm5mAg==