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
- dba5e811e69bfb8c1bd2022fea4bf2046e857bf1b7f6e807b017abc274b00e1c
- request
- 2c9e115151f64b1557836aec003556d3756d99a9553568b0ada951694ababe1f
- transaction
- cbf723766300ca6f2014eee5f73c4194249def35c31eec86edc8b52baf267355computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 35742
the chainentry 35742
- sealed to the entry before
- 8029e341c63eb9e7d75f3b4247c116da5dafd750158a4df7a0ac880aafad66ba
- this leaf
- 25186a5c6f6791557aa42e491acbb2da08153357aa6bf192fe672bed02499e23
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- BXwYZf5+hYSWjx1m6jMnUQ2QVEE/FA0gn3IFbGKIJ+BUBAUkOe2fGYCQ9vWHBjiRoTzNRj8I282f+7TYp3/EDA==