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
- e56eec5ccb83ca680771c56e2ce8ada49b6a356d8abbe2e0cdc5f7761fd9c251
- request
- 5b1d82d0f916a0a91f15fc4348767c278585d799851d0adc08e4e45433b3a97f
- transaction
- 5ef7f6a32f66417453ef63ba55dfba37514e961a89a9ad1c2b26ebe776fafce1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 32453
the chainentry 32453
- sealed to the entry before
- 4f48976ed9fcbce96cdcfa7047d645d63e43778d9db4db7a86c2632c75b2617e
- this leaf
- 0d610ceb9b1cd68177ae466bfcee2824bf5ab53501140fa95a1e388b1f3ca50e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- e71WCxHLVK1QlUptMkBNCauu8TSG/A8yoavhIDXK47D1xVYc19T36P/e8t6MjqRefGw+ap9zDYHa+aq2yE1pDQ==