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
- 5b183e057161a6fce0f1667e135bf87968b4133aad4670c9d211906a5243b726
- request
- 4d22f6d9341f2c1bf52b99b05f5ce659e57fe8142b5e8deb6a93885f241ad19f
- transaction
- 49304317a199f03fda50c1771aee876124650917acb322e44968ef93814d4e55computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36511
the chainentry 36511
- sealed to the entry before
- bb6fa2bdf933cbc950082480bbb99a7c445ff2397192ea8b175595179f477915
- this leaf
- 15974a0551b99c353cb1199ee0025b29070d195f1e99e3a289359f7d9e3ae7d1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Gf12/UtZY1l5VTxOrkLj9klGofOg8ypBo3RgbiqDBujB/fdND54g4f2iRWXIWPUWls03JGL3p3wO/282Q+liBA==