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
- 512a48ad081dd1b5544dda226f698560c7db45d1261dda4e11d76e6a04d73803
- request
- dd95593a9a4b7554a32fde2f99198f104f81bb9f7a4be81a2170b00c407496df
- transaction
- 7f07a3dff86267e1ff89fb4e29876cbe84a53de1785a06477938857364053fa4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 75386
the chainentry 75386
- sealed to the entry before
- 73a74ed093f6f2ec1a060b6b3a1675572461c5ea3002cbb898016d9015d8edb2
- this leaf
- d7dde324fd52b7c844e7494c87f4cb4efae1241afc185c7036610040b7b4d06f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- xGH9m+Gy8uLnafYTKygwI7RDDCjEXtI+Tl7X3Ef8iXBuz+shXR0VA9QMqbOVYigbeZTKMfSalkGCxDgMSSn/DA==