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
- 3fc9149d43201756b62ced8ff8e8f78d05540f5c92b7e839f5abdf0a71b3a7a5
- request
- f5f2f80a5475228c712db1f19c9b9ab69f0371eb9c63dda1c12918d53ff5ea52
- transaction
- 18d0d8b0cd8bc1b55bd9f1da5681ea4ea4e50a22833aaf3bbf83111697ad632dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 53474
the chainentry 53474
- sealed to the entry before
- dd08957db4b7e3cab56b77d0d8adf4227e32c7ef610ab84a3bf5fd681a200478
- this leaf
- 4446ad5c7a339074416ab05ad0551d3276db2402fd4bf2ac4fe437041f4d3840
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- gbb+cfudlL0Inbki7dqa5Xtec2JbGWNtR3VASCQ+LdoBgZ0CkKMr4DqAqGk65dSEHK2PNCSWZjBv3wWxhww0DA==