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
- 364f3a8290b65dc68a9eee44465181e3fbed8a4ac9c6733a4659a5257952b080
- request
- 7304cf454e45839f469ae32d5bcdc47058c5c014f3c212ed9f63642212cc7bed
- transaction
- 1e0897817d741d445af4466aa351dcf9a9e44714755d4fcf139bc57ecf5f16f1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 61816
the chainentry 61816
- sealed to the entry before
- 922b82f8fd98fe7421b0fbf79042894556150c3eb7688d10820f1452d5e1d0f7
- this leaf
- 77bb020c9af98e5631f0e886f68e15a3e60ea33e69251a63f58aea09623bf550
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Q1kYaUwIUOzYTzqptctfQ83GN0/82KXCiM1+NtpD+khuwkWaXa8oKXt/5cWukCpVPEWk+MEj76kJWwDYG+F5BQ==