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
- 0d1ca64d4a236679399c17b34b8285f2e15a1b25666ae5c8cdc005222646001f
- request
- 1c2eb8d0e81d8c0b856ce48a9ac50756bfb30d96d71ce3807881935156320653
- transaction
- 6adf95d2cfb0ed73bc9dcbc2626129035902f2c913c70e8a708de5dc3341117acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 73655
the chainentry 73655
- sealed to the entry before
- d31e0a11893ff275335ad7e6058840e9329917f4179a9f86d1a7182a471c26f4
- this leaf
- 255d39b5285d521d75e9c0b9a20153bfe934f264156011849598ca7289b9e063
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Quum8153JZcwd7+NRwWT1iv1s8J/knll9vMpEBtLIehikjjgpPESX4b1I4de8ObkXxMOaHdZ8+45n+AsAY7hDQ==