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
- c4274de8127d02c8bb4ec56485b297de239044cef68712da21871dd12319ce16
- request
- 30ef2497451b0c4e90079ed1a5870fb02190012e80fbcbaded5add7a1d703d80
- transaction
- 9f497ec79621d6ad1c7797daec3385dcfa553bdb17cafe7f8f9ff29c573301c8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 38197
the chainentry 38197
- sealed to the entry before
- 8935742452c5e0da4b09a368c619e0cb4be76a690cd7017c666f6e898c6143af
- this leaf
- a6475bf1b6c273740c05963a3cc7b9848535a1fd48d8fe09ee2d50e444509552
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- wMyu3gjNV43e6LZHWADgRPFR9mh/QMjUf4j8LFxRTztnRGldD5tZWLsucUsWg40bt5nOYiuXhxbih1LENLqUAw==