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
- c922554ef9ac35fe93d86055a7e6cb35169afa1534187afe54cff0e43663a856
- request
- 91bedd2526ff56ccb49fb973b3ebd6cf85d25fdd9f0cac03e2c5f4e761a70aba
- transaction
- ec1a487560f100eb0809387d3d37d60e37801a128a4758395832695a70a37bd8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 421
the chainentry 421
- sealed to the entry before
- 3dfd8c0dfd7ba5ca3e0aee197784839dacbbb4c64ca90ab00908129ddc839e54
- this leaf
- 7926c7f3fb707cdbef781010ea5ff4110dab323befab7d806acaa45958d05a87
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- NTMEdzNgbOvWdbP/3PRQx7bzzOiILb9BxHvHk8ObMDJk5pFcjKpUANZ9WiaWj0yoMjyFLvjcthvRJYRbxnV9AA==