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
- 71dd708abb0f397f2dc53f7a680ac36ec6b8ca12fc1368731c6f7852c8e0cb75
- request
- c0321feb6454d9b815ffcfe253ba7dd128cff3cf6fb62dab06506053533ee4c6
- transaction
- b7f38dde01aa895e0997da5e5b4455edcae062993f5f955469ef4ac840c053f3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36554
the chainentry 36554
- sealed to the entry before
- 643c16688c3b0f96790d8515cd0b0ac595043213ddcbe4ba2cd8ba6c469fe990
- this leaf
- 00a79a649f53b5fd41b76835bcde3c411e1983c6ee8b91b370f237724ce59126
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- hzroWxdHaP7yJM0fzCp5MI4dzYDlE2OIqBWOZ1OPqbuxK8gGj8mZQZd7WstW881/ldZJSaOFxJMTjUoXcID+Cw==