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
- 2a506f664c68f6322905c6437b4d4d34c618fccebbf4410f467e94da75391eec
- request
- 18ad43f64e72264e6eaea94bfc3cdbed0e5195560b72f9591f28d240cd6c3da4
- transaction
- 0b7dd2ffbbe7b078a40b6782276fb726dffccdecf471e24c3df5b970cb3645ddcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 4344
the chainentry 4344
- sealed to the entry before
- 89c2df214e53b95885a5269172986ffa6594abb1cd125f33b56a689c1a4ccb8a
- this leaf
- ca87dc867b4348391849b9315549dcf8cdf37c4f65bc61faf62827ccdfea03cc
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- G+vdiS32BABme2KwnaL95a0Xe0tNzfmAq6xzqrKCrbfQmatTNj8sHxp7IEQbIrLq15IphPx8OGsOmkO8mA3mDg==