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
- 90df714cc6f16400144db4d8589f8cfebe766fa151cbd281736d7be1b2971761
- request
- 8656d2f4fc10fc5f2a4956ccdf388dbb42bfc2e4ebc749c3131400c2748ba339
- transaction
- ffdec6a9b132c5bfec84f61d2e299f6558732f418f394ee388513ea647a7515ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 55743
the chainentry 55743
- sealed to the entry before
- ca5b799ae581f471234ee24ce98b3f33b45a806790670f6759e341bd4bddf638
- this leaf
- 7aba836c8f0a622e7532a8dd67396f2b0038706857eb0d0c707bba0d2821f6a3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /9SLmP3ZoMgrhl6+xBXWVO1Mp9lfTpyo/IEU8+ERCkQ7slgwcj/HkGunqOqR8TyOqYSNY5vU0e11F31Z0888Cw==