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
- 732e3b0fb0306c53a186753d728bb660100a3817fd4514d26d9d6e9739821b89
- request
- 2613d26b3e68850cf6df9e29c654082b3a1521845289e1c0702133cea0b2eff0
- transaction
- f4bb990820599821087acca03a2c7d74d12e88e7311c257540de3a9f32657c7dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 69983
the chainentry 69983
- sealed to the entry before
- 188f6d812e76cd2dbd167084352e68f01f2dff3964dd638edbb4f51b701bf70c
- this leaf
- bd77d65f32772739ce00d02e3f53ea9b1ea1a8eb84d714e10e93e82783f27198
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- U4ixAuL9RLBozc/4jbGdQAOJAMqqzd9iA5IohZkxAwJJBTEn5aE3aypi2KXaqrG2GrGOv1WQ5j0w/CoChVUDBg==