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
- 0f4248e6f06bf46787711316598a7a3132e49c1274755ce672de77e22edd34a6
- request
- 0270eb0a1ff5ce652effe7d03d76446208a654658668a8e204705ad132d7a724
- transaction
- 3e6258d8b110094e0b0023c602bcce9fb2b33dd7e2776fd67c2f7f7fecaae270computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 13851
the chainentry 13851
- sealed to the entry before
- 34fd252870b782b0436b0de471b49c27ba06e471299b3fa28ad868ae11569df9
- this leaf
- e3a97e2782501bf7f4422e4e3eb7b26d491425ab63e57dd74b310e541cfdd654
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ero8mrio0Lmi0p7xSl+MkUPviHdik9gPLAYTgHB9lbc6CILQtzXkQyOajGf1Ov9bsyaE5vio5433n3ygqFm4AQ==