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
- 32d9554a64104da30ce05d9874cd7ea9bbc06720854fa02097fcdecd219da00e
- request
- 704cc3da6258d6cca9d2d314fa8d00ec2bcb1bb3efb8ac99b0690bf5674d43c5
- transaction
- 61a3a2246960bd935b2175fc18d9594fe51a3402e95e331bd26139f1261c6344computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 50150
the chainentry 50150
- sealed to the entry before
- 414f91ba7cfd38883fe8358e1eb2fae706270e138320419f4ab1b458768f1e45
- this leaf
- 988afed10bdfda51ea80b61524e34d45ae08522da13156f88c1f036d73f52cb2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- i1riNWAnHfMslQ/yERl+j3e6zMV3xM+fPjB6Hy34Lr4Qr4SZQe/yZvGoIa0dMa/b/+JUynb/VwHQ+TGPKNaOCQ==