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
- 9c029c7a7cf9cc3a718be365fa9a8f37d028b938e68bbd8be1fb391ec67866ad
- request
- da3e8dd8bd87978b78245c26d506f027831e9abf18896d41f222d3fc27112d81
- transaction
- e1b9e91df50a1efa2ea16fe78ac8ad04ebaa01ad2e2c11fb2fb8ecd5ddde748ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 77821
the chainentry 77821
- sealed to the entry before
- b27cf2aa952966f09373ad9f9c3bca682d209329effb376c485f00e20d275a44
- this leaf
- 4907d3e35945fb7119898e569602096a8720b8a879eb92ed872d5c2e1e1edd2c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- L60wT3Vf6hwv7J1nWFPPoznnkYk7er5Gus/d922xEVRZPIeXjVwoKWbhfUPjUafJyqBVzw24zfx5rCND7rRGDQ==