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
- 8ec5441d1ce3e8e292b15e8e5d54093985c95a7f46575defd8180958a2cbdf94
- request
- 6ffddbf71d971707b908019ed7023d06b72ae1ba8162bdfcc4b5a1f42cb458a5
- transaction
- 2f53b152327d7b350774605ddc540007c391142837e16a1ff6902bfc70049f08computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 75966
the chainentry 75966
- sealed to the entry before
- b2252a45fcd2a3efe095a93b11f172dfc40b3afafba2ef32f2758d4d2ae07c58
- this leaf
- 56abab8894961a569107352345a8c424acc44dcaf89a613d321cb8d32d167823
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- X3JYaTr6eWidNcEOkOp+WR1vqoyDgqa2cJK3E1HE39GnGgMouFsiGNV+A6UADHgL21maCHeiOaenIoEy7VRRBg==