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
- b77f4efb6f9006ab0c06b4c66232a117b7c32ecf8abd1c254c65225b94dbe744
- request
- 356577e39219ed4c07b66798f93ace4d378420f5c2f52a294760d58666533271
- transaction
- 114a712e10e613b7ceb3b9c5279476c120511ef313576215784b28863c44203fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 9670
the chainentry 9670
- sealed to the entry before
- d8e31f6f3d37971a2597a261fb8cc1e631087a37832a31af9131af092f1b1c09
- this leaf
- 5ee133f0fc1e749f7d208490472df0e68c0a5ca2f609c3cb5f8db42dcc30c761
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ibx/UwUJY7Jr5eV0DH0DjnZVPslZk10E0VYXQ4GfmTnW/lp3HPHxaMBsyPM9fyiEXDHYeLMPwhe7UQh2WmiDCg==