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
- 47eaca20ed4f9762c07981d7d92d6eb42c9c822181417bfc9eff98cee3df8286
- request
- b032515c06040f00254301c07ddf25e137196bdcc2c14586986f1dd7a4494b91
- transaction
- 14b6819e01a8d141e98efc1b0048ccf3ac20f03439b0fdeadeeaa007afc963f3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 50622
the chainentry 50622
- sealed to the entry before
- 6c8568b6d283c66edc9602d5565ced8d4361933be3b6c3b53f08d33bde385e99
- this leaf
- ddf353b5e26f35d6db18ff81935f6f65fa8bd6bd64b545056ec65bab5e3e6c6b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2jhp/1rawFZVNoCRgAJxx13VC2xKgv9z1Sld62vZ/d6ruasJSdY8izONfxaa4OnziXHSTeq3D/b/Xntf+fjjBQ==