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
- bada5efb29d4ba377873d6a9dc218d86c318178b0612abda951fe4ba51c5f3b7
- request
- bc5f11a24437aa198baf612cc537232ad384d449ccf759f1fc8599452b0b08c1
- transaction
- 532b61e09ebc0c15c81df4a5f1c67095afb39b5f8974bdbe2737f38176d89c42computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 6662
the chainentry 6662
- sealed to the entry before
- 56ae08acf47c23cf1fc0a3c6001b3e4c9fbfbd8cdfc71aef70477c33e174ddb4
- this leaf
- 0752b670ef016c7f228544b605da8168216b45f0a7cc67a420dc6896a10e3c20
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- YYalWWBlazsJgw6BZiO2uH6eRi29pKrIcXorErtOL84YC+n2fNFXCKQBnt2we8Rozk8gZSf2WeLoBSo3QxvGDg==