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
- e0329f8bd24e4e337421886faf3c28cedf5d3d05eb3304f1035710cc5ed4c502
- request
- d97d35a57ad930370271596a0d7f92fe179c819a4614a4076193952374244757
- transaction
- ae412dcd2c273c13489043b0c68c442b6d1c08dff789f3c1f03545505768c1becomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 76911
the chainentry 76911
- sealed to the entry before
- a1ab5855c2c9d913f0325fc4b9c7fc4d80623a7d33d881b46cc1e6370f520585
- this leaf
- 9c326a91ef6bbe2c296221d4f35bdd2badb421841ed69b354d35e4dd7dc61299
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 3jLXJ8K44fXmswxTiJpVLiqCdWCKJ54WSFfuPf4S0Ms6vcxIymZLrfVIetDlsX2KZrLZHEtGzRhCKLU+foLcCg==