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
- aadb2a6754c933506eb12bfb27a67402359d9dca5077f0ceb4ffa99d8b4f3470
- request
- d7731c3c0cc32345ea89f848cae0cebb37935148f1441234ffd36bca7a097b83
- transaction
- 138d43cda49562d12291c52b38417353d14e31ae4d709645dcb20e2094c80d40computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 17505
the chainentry 17505
- sealed to the entry before
- 4339aa10306ca3411c640f3c562535cb342f8e262eb30225c710e7db4acaa723
- this leaf
- 370153c437d59b0ac51e2673c38e6b1f38baf06f7c2d84398e24faff2ab959eb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ushkJWY9X1bXST3hKCDFUVGFsfRKeXRtnQDaOSwCmjsQimWRYtlXIECkFmkNd8QGVb4loHe33nElHDNP92BzDg==