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
- 75d78f105af901c3975a4b9f991a2ea5e6947b5eb33346979868ba9ce3efd75b
- request
- 160a4af9044af01e1be1bea6581cea37373e5ca2a4948e9e0c6ec4c7a29ecbb9
- transaction
- 8a5ecc9ba7ba7176fb299f5bb5d6c8bca3b9cc6ba722675d86ec728617d4c4d3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2445
the chainentry 2445
- sealed to the entry before
- f26cbeddc4064a26a3bbf8980d4c85c9c8c70ae4773bc36d4239ca444a2a96b3
- this leaf
- 94f7a57bb69a7932746215fff20c2c2e755d006165109a3df41baecae634fa56
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- WvI8DdSAl5j879jWkuC/7n42JlbCGICoLy0fhJGf6hdzQPL5eyyQZTBz18LFwNBt89GORdRDNrhOdJayYSGlBg==