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
- 7a2a8e6512f585c0742af2e8d93143e17d7508a4d8e7d434001c0a8bed9073bf
- request
- 29a8d0149416b976e52ef6447caa79464b2cedaa8c1160f5c6657fe4163026f4
- transaction
- 99880ad0ce1c7924e752c183d0ed77dc5a6abd7ce64342be36d37ce69baed45fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 52903
the chainentry 52903
- sealed to the entry before
- 0e56b1126f4743863fe1b5f84b35791c40f2c3464ebbd035be9fbec5566d0a26
- this leaf
- e0f7697e05b831695983d370928971a7e1ef92cd44b5236c36aafc91f88414ea
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- fR8RhlFBBBT0EQYZc3EKLGpsR+BuCdjYiocUlGu2tXD854iwvfWWsSPr3Pj2DXI/RfvusgJT+ztieGlPLfckCg==