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
- 8ee8657d111923ebce352277b3b84ebb558a80f1d8be7790d5a14147dd72b4c1
- request
- cea0489eef4ad688bbeec44fc79186f5ee620e5e90ac0acd467f09a659c3911b
- transaction
- bd64ace6ea12d6f3620323f5530e3dbf2326214b340263edbe92584e34a1ce54computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 18275
the chainentry 18275
- sealed to the entry before
- 05bc1bc95d21c556d75fb080c2f0bb53d9942a4401397f5036b87a7ef769baa4
- this leaf
- a7655626aae52e6f73e18b2ad95abb422d49afd8066a1f0cd65018b0d5699bb5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 4nxS0VdQXU5lSDqpgfaMhDMOE8wb977barbiYQQhZYWE8w2Ma2NjWKyEcpryGWSiAnncuXww79QI5JdgkzDbCw==