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
- 967f1003e1c86d689a14f52fc7591058651fb7b9b0ade354019e0fedba2d166c
- request
- 7361c88910159bf35ad092645cbe1f9106ec40f1fe98cdc331847353d43169a8
- transaction
- 4bce3de051c1f237226231116fed6fcc600730e24717f4a594e8066af9ce8e54computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 25398
the chainentry 25398
- sealed to the entry before
- 2228e959e77c847b56a82609fd5491d051d8053b899550efc76c0c04d68bc3d5
- this leaf
- 611a4cb117edf826898a461415eb8c778102c6dcdb6b39ddd2adcff404ee448a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- g/8VQPyQgvNYGyqv1xUNr9A06ITJRuIKMmy4wzy5C6bGtKVNX9xAn3S/PSaKUkhdvShQPmlylQKsS5C7z+cMBA==