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
- b816182fbbaadde3843bbc5e317e4c39dceabcbbcd380f1eec05694105877322
- request
- ad3be400f6d74760eaee0437da927ad158d9587d5a4cbfacef998ec7a89edaf4
- transaction
- 222114f5b1ca5747a4102c5da670675f03cbc5cc700c82683ad533f417dda7d8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70432
the chainentry 70432
- sealed to the entry before
- 9e43e52a5d02e0b59f0883d2bf02f53f87ce16c55c7ab86ebb55cdfb6fe61e56
- this leaf
- f04aa6876c023147ea22f664b5c844525324853ef1d922a30bbb1bb529762d34
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- LujICGxkuPSWDsEUJEtsR88Mj2zB1dRIj5RCFgYLzC5cFWhS/bby3Jn7pTt58wgIH/Q4X4FAo5DJlpwgApJMDQ==