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
- b69e0fce8650ed2b5533f429cf2a7f51a2fe240ea27f2de5771c3a88ba4ef4b1
- request
- 9a99cbf43ef7757e923978661097a57df3d45006dee7c2779b133edb85ac158d
- transaction
- 88944e6eca0ef71a60592544896c8a965b4c2cb8b8ebbccf8a7ca8f7e930aa01computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 54423
the chainentry 54423
- sealed to the entry before
- d6a86e5c8f84b842a7fc57c5959f9232fb54f4e14e0d5bd5254680d0b26d6db3
- this leaf
- 1f5689294f7faffb177d3e6914c0109d55f3f09d4fa20a8d2cd61c271e32a9a1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- q/SjZ7UzJp7ubR5Hg57JtdsWEuplx3xwZRM+hmw1vDgCCoKfmbWdGmdc7qjViEQLyOEZzkFnbEevJubHQGHBCw==