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
- d6a4379f44f1bc845d0ee2d493c3edddfd35b6e62d0a087c06559dee4fd61002
- request
- cb86db62f6f5aca9840519f797bab4e86b692e4e104f93576df56e4d0c14d5e5
- transaction
- 971a25b2b80a7d353bcf085072928d8e8e585f7153fe69dde8640bb325beeea0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 14404
the chainentry 14404
- sealed to the entry before
- b3c3682a635ce8f744c1d2faf2cd90a67402f52eecad212bd9b2fb4b49ca5623
- this leaf
- 515c7e87dfd05ed161e4bba7b9067494e3712c811f4fca96e99db2047a2d30c3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- DNSL09NYTAKLe+O/NJeEtH6xUHvHQn644AuzICSb+vsewCEli2NGN5bqTD2sSo8Mc9xLDQ9tCEgjOa3V9SXOAg==