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
- dd36e63a6d208452c43b4f778ff27c40dca29d1bfa6b9107529440d19dd30fdb
- request
- f749aea847a646eaed40faa91785be297494e1c969f97cd91f15f96c313c66a6
- transaction
- ef84114e02cfe0b019fa0ce174c245cb1f43c40754211be5cfed15a078874930computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63024
the chainentry 63024
- sealed to the entry before
- 8cc7ebdcce1ba16740c334dbda8bb014f20ed32bb02f4940ea8d3655a98ca983
- this leaf
- 64cd5b77b6dec6449834b480be364919ece4a9f5c9f4acd880cd8b51fb09fa5b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- RvyJgKF4fEkmjQ8ifA91p0gV8Iy/FBx4n4LDZauJ2m/E7ZvsJ4kx8VzcF+CnS4Bg3sags6VSyXCmZhIYLznxDg==