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
- 9090b1b47542405c7c7d9d881fe99494cf5ec0b2a20f920c457ac49cfe1b9d5d
- request
- c454463429b122c8b3344dd39b88bb55473bcc243d9c93eda45fbd1899f0b1d0
- transaction
- 180565cb9ce8fbaa58f1a3c5de03704468e1ca6fa433cce4091ecaead980b4aecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 43600
the chainentry 43600
- sealed to the entry before
- 2caea2d8c054d35cd24c4a054e945483efb3ec771707332b2c4c340cd9ceb80d
- this leaf
- 89692e6b3380e534a44a84dfc8c6a733ea2eb45f1ae7a55a883f83b48774362a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- HKcpkXh5/mn0uEeHb5LvFDY51Od2DWDmaqShLN2ojj7hu46S06hER0hkW3PJNosAPgpaLSJOuCcDJVMzASCiCw==