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
- 8ec4f6b7b164d76d67813b1663d5f53761cfb7d81a6a3da717b14f1134c2bac0
- request
- 1f17f32096c139d4a35df700a0eeb072f5ae96cf314323c077b0d895faa2bfe2
- transaction
- ed916986d82756b9df510d71e319b002794df760081980e387cfdd44da103b42computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 52417
the chainentry 52417
- sealed to the entry before
- f70aa198938d88fba6a8f2d1dea38567d6d12316fb8ed3575241753197099b5e
- this leaf
- 36c25a92f1424b82553ee5bb64d42cbcb9705e6c390a1f78bdd4e7d023274fe9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ZoOmuscAjC52EuTQ+WoadQ4AvbaK6jsQZxScTSpdH+DGTDBh4iFd7vSxFLC3bbX2DdOsr/cLG7juLUa31/m2BA==