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
- 9f7335b788425f456db1989f5a6183bbb6e658766ec1d8be65bcc474c4da2401
- request
- 2b4573ae290acf931f92cdbe48e806a88bfb7d11309579815db7bd21af2579f0
- transaction
- 8ded49a05c337a20e6cd0acb9a23be822c062433f69301a77bd90381fb3dd478computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 18399
the chainentry 18399
- sealed to the entry before
- 638d953f5b83654eace72d872001ad5cbe6d83680d35e9b94482115218ef28fa
- this leaf
- e2076b7c9193c9542e818b21b5e60dc8d6503a6f287db307ab3f109debe6b1ce
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- LdDYpq0AiHd+tQx3KlABd7V62mjMJbUAAdVi5O7Mozo4IbB02+vf/gh20V+ImwxHMsR3sCf0DWyB8oHsWbRKBg==