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
- 62f36bf34476d354d509e4205cf5ab612f5629d549a97f35af3480ce71f74048
- request
- f859a3a551efec7bb9bdfdeebd1152872586c05cd4b148dbb7107ae1b31731ab
- transaction
- 2c6b1f3ebb922b8bb43eed555f1a5fe37cb0c6494a0971530a15522c43fcc945computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 67178
the chainentry 67178
- sealed to the entry before
- c918f0fad0f95049baa6942733cacc6861889773f3602c806554202505f9ccc7
- this leaf
- 221d226e57242ba57d10ea95df98c4150a9ad68f75d6a67f41cae0515612dbe3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- LrSxrpFJHvF4dy/K4REjnLrCX/68570088+QNdtQVcEwz3TfySnGLde2Q/F4NGZrSPs+s8nayKE0bv8CqyUGCA==