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
- 3963ac845e476d66cc9a6a24d9e5f300b0d8b30a3a6f7bccffe02fd188e2e65e
- request
- 88e5adaf74e8366e44f3bc91793e0deaa060d1016853c7c0948d1d173f5fa8f2
- transaction
- df0fb778b03096fc2484b2538d7ff5fd55863580747fadec88cefe1844b8ce38computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 6255
the chainentry 6255
- sealed to the entry before
- 06716ff78683a5bc7ae484e579c1884319bd1b90e554ed950f485da44dc0ea39
- this leaf
- 13d0d8d3bc6410d55ca57572faf762c082221efb0d60104f5a8d3b682993d489
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- JCVbFPjxqbwVtRORxjYwJsz9G2EwihQUHydlZ5hkIS2bh0NZx2UQSGYRkfORtzVhXzZzyLm0mw26rnc7mud2CA==