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
- 7292b2ca7554cc2cdb9a07b27ade11d59bbb7389bd7cb0f5427eb02d2457c218
- request
- f14a0b68d0339879711cdcb8cf9acc195d2c8c58b3256129e4b648f89b428c25
- transaction
- 219efb6aa42e87bc268dc0797844564115b0f599870aacfb4cc3bb535c52eabfcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 48084
the chainentry 48084
- sealed to the entry before
- 7ae64a651e8ea5b69c3ebfef65d453e0f326e7bf6be3448985b75c30168319a6
- this leaf
- 0566d9c18989e9a094ab9bd0426ceff8b02299a336e9e68c96fd44511f071d20
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- fFNTLo2smSNX0Ihx3rxy/11L5iA67bXYJy1JHovUXHZx60xGUafD0dmeaKKr40BloeqXd+z6pwsYAKXIQUoJDg==