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
- f886456d642f438a5717a4da35f3946075c059c719882cf2fa0a7904c8e0766b
- request
- 2c6f0f6ec57418e675e60dd4fbe520350f063ceffb40ca9a0679eb6a1c50fa63
- transaction
- a3d5ff89f3e83429f28e1fefa57d8fefcf436f50cb4d3d6e72b4490dc6fabcf4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2295
the chainentry 2295
- sealed to the entry before
- e3a6e8779b5e5630ece66532ff7f57900b42824aa125c16c1f0640db82c14fb0
- this leaf
- d9f3a822906bf6c2d266efb8074fd721bf09ec712845181125e8c3ca9c12775e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 5hwE8ibMyPKZCmO7Dtusam1PlINcT9yWuf8blwFa6WI5GlZRrr6bt9cdZHXbkKrFDlBvRmRIlIQFmNDaoLdSCg==