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
- da21c1b200843543f7597596700cb19d3a31f03a046e6b1c17e67d9ac35adb75
- request
- 28cbe3f539ada778cf67a6e14ae180dbdc14666299720a38f43f3e5298825045
- transaction
- 70a0a33d4276f7e5c9440133e978c6ec298c04d1e2051e3a7b8324aa7759b68bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 75679
the chainentry 75679
- sealed to the entry before
- c259abadf2fc116d932fc30287e86282d137ef6a88bb6ddc348066f5c6935492
- this leaf
- 4232b0e489beb33ebb8cd90a085cd6d5c658d462b668e30f1258ec57c5aad348
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- TYRFhdlcwDjyumO/bZggr1nkuETy6AcOX63VZa/esdyVNJJkLJN19hy7tEqfSkMdRsh9ja8CJNuDVFOpEiP/Dg==