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
- 6bad31f76c59315e90290c20cfa101f6e42dfdc70541878e0f4bbaf3ea48f1cc
- request
- d8b4d9f9f3afc612dbb38b6b80a81b57a871f4184db160da20ae610444641343
- transaction
- 86ba1f0a212a6c2b53b2a841e87002290108429c6c74a8a99769466a99d8dc2ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 17705
the chainentry 17705
- sealed to the entry before
- 69846e2c9a2e4580edfaab8445b6ea00301babb35a06165b5be54fbd92f10f06
- this leaf
- ca425d124d59a3d84354c6f9d9320171452fe312e93e1f8e6c28075a9f06b049
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- m5+n/tNmV4dlcownK4/PYXWyloZCEAlefEZzx9foGq0451pBcBM6ZXBlhJ7aXlph7nO7TqigKDRbQhPr7ndKDQ==