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
- 2dc842866d694f169a0f9f1bd64c829c018c7385eadd8aca3d6174884d8e6309
- request
- 5b95db491f14dd0ea69cdea3ad4bfeb1ffc320863af994707eef445717b412b7
- transaction
- d25ac6dadfbaf4c14a13b530a3144e716205ab56b2fee9154b94f189c1058eaecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 45176
the chainentry 45176
- sealed to the entry before
- fae082b15c9e69c27e536df8d9bcc2a2825f72b85e6580568bef9a26b87f8f20
- this leaf
- 647d725be6094dd91ab62915ccbb9fb489606997da3411e781eac1d260fd3ecc
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- DfoBfmOSKLQR/QRPh5MUHnEy7lLNSU9wIjQm/TxPqVhmVZ0jlBEiGuhgAm7hug1GN6oOq1yxGCiTFbSv1jcMDQ==