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
- 9d81430823b4b9e9c1fca0bd02de419603bc4adaf281ae8aba4cc2eb94cdf36f
- request
- c468d94ca8e61302b04fb9b5cff3afecac99843fe2850c654b1b9b2a31ef796e
- transaction
- d20276a92d60080415dfac1699b2a345694ffa5a55d83992fc1019ac101a57edcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 46810
the chainentry 46810
- sealed to the entry before
- 1e8b4cd345111b4a026e3a31e8f7d1a621eecaa9ad853f020b367f24c0945bf9
- this leaf
- f4e5d8a02de75fe9b3bb9ac9ea172fb7bca0f7143f0d63cdd160c5f95dfb2d05
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- f5dO7hDPlYRIu83SJubCQ3YFPMi5cQ+cDJjJb5yGYEXn7U91NJmB+XBvSpwh/OZWaIjH6b5iYw8ZRX7pUC3mCQ==