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
- c5716b3b1f110064d49f7f47a5f0f7e8051b5a64d76a029877702248ccbe9368
- request
- 3cdc4136ed817ea50807117d2e54b2c4dd4592d2667d2122b401c04f947d3293
- transaction
- e6d698168b625b79411b3b189b8c028e71f839e8320f45064f966d1ce83af9cecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 15684
the chainentry 15684
- sealed to the entry before
- 6506d65dc276904476a67cfd68a6ead0cd95ec643db7cdb9dd220bb97a26c10c
- this leaf
- ebbdd67fecdf9d6a0dba5142cf15826259d9cd019484d58608a3681009d2d948
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- a9sni1WT1RH6RV3LsI29ptqiKKMdAAd0SszyHxxGjrLkPE7PaX0AGQM3EgOWkvB9Qm6/Z0NtTHvExw3nze7HAA==