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
- e8639f65e9ab71c1040e145d8eb42e586d8849a33ce30ae46fdc6174763dced9
- request
- fae1acfc1d4d7239e921f6434f24e1199f3341c99e73aa6652e3b9ce918101f1
- transaction
- 2c34e9cbf2733001349522b462542cd9740d414d3df9c3fea66dd831706aea81computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 32080
the chainentry 32080
- sealed to the entry before
- 9ff0f8c983cbb19f637e15ae3274af2d54f46ee0125fa7393607d93cecd41071
- this leaf
- 66b66ad3d8a71ee8b05ffaf843d72bee94f2dca8d36ecee81373ec84e32440d7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 5k63w9a7kz5EmIw3SYDV3wfl4eVDg0TWy4LdUlhCvbo2CyTKlcScb2TBmaBXIqvAXu7Y/jGJtBfJlQwRvzxYCw==