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
- 297de476c4608f5196be5da408f69c0b72a791f42ddc02c4e74698925c3d33d8
- request
- 3150ef166390e54bdd07c79894274a77389444164c233e01bf6acfdfed1d227f
- transaction
- aa65e2d1e8b46a2b03842f9a0d779550dde492a4cd8c1f54212017fac68e3bb7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 15155
the chainentry 15155
- sealed to the entry before
- a48ad323925f109225aaa800e7942851c87da6f0ac9bd619f202e7c2248d7d73
- this leaf
- 9cdae8dbd56b0c40d80a933cfd8dc744ad6947204c2ce77ae3709d1bcc800531
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- eCmR5qYHA6d3sgE/lqAuXREi8cmNWgIxqkoVMOliAla5kVrjqEFMI2lIwh4axBJ1xEhovGy/Wg46bAqth0inAg==