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
- 521ed1c6742f2788a113625f1a0cf089d5187d2e88c86f17ff07a08d035ba472
- request
- 96236fe51ed0f531613d12400cbe6a25d0da8d75834ad9482694e5c79b2ae460
- transaction
- 238e59b65c3fde76a2c600ae7c503fac1e2afd968dc1ba146ff232f504a828d2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 45497
the chainentry 45497
- sealed to the entry before
- 8279f75fb26fcb11563e554ce506ab37e0c8e0493a149f9f8d048bdcf541e016
- this leaf
- 2f4c0659c8f7d77bbea3089f4f88e3a991e7cd24397fa1c0494dedf39e7e273d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- QJipKN68s+tpBMUzswZNPJGKNPZkr/ky6zTkId4ggEHAgw6awxptezANgqRo7SIL60GHtruLpXreBavKQvUjAQ==