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
- 2118b6a394c3dd73d2627db91becb8ad5410d5f5545cd27775cd90040339c229
- request
- d1b3a7bfce272f7de7429dc50782ae01f3c204ed5f3ed8ffbdd13816fd812b99
- transaction
- 3ddb809efe9f13deef0e4df271ba2bf68f4c115d671965a3665ef0a9a70a52a1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1285
the chainentry 1285
- sealed to the entry before
- b9758a0c25ace5665f979f0ad3f93131d454afa9e42034bc1750726b6e0cc6a0
- this leaf
- 1b2501de0e5895130975023fa80f5e9eb02769579faa4c6f1cf06173897f026e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /CSYvsRbtA0AZmbSFPIIoBSsGFvlgUfH7rqZK+H6018wg/ksGteuWwoXrkIzxH8oyaiXYEkTYa+d9gA3tupkCA==