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
- 259ffb8a02981df65abe31b47a553ee83d7fff31e573f25fdadb194c91d73a42
- request
- 27c5750cb8029f3e7d221d7d48782c8ca1858de5524d586577ac2390e8ac3872
- transaction
- 1e9fa050732f34d18fe87e6709964af67a28f0dab72befc482d09333bc292afdcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 33760
the chainentry 33760
- sealed to the entry before
- d071caf8869b3cb280cc2fa32200ca2e771626b58728e55f35ba68d5eb156c07
- this leaf
- c1a58e098e4cc3ff0fa5f2259c270ab243ebf248891903a8c1f48a9ccae3f3c0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- XXrbvO0Fu9kiw3FTBTc0YGMwIkMf/xdgUmHAxdmJq+TCIlQ8E7d90yBnASw9TIBYkc38zgAJOzZ4xG85SVY2BA==