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
- 184a71854c3ea63eb8c1059fbb1a42e130091ee9326d38d5051bd1efe34f872c
- request
- 5c32235cff893459414d1be32dbc71ad19dd0be3719b40ae9cad2f66db488cdc
- transaction
- 7a75e31eca51d08324a9cf0e6a41c0f0342e0e6f59718e5c18631b2229504d64computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 35958
the chainentry 35958
- sealed to the entry before
- 527a81909a2ea0aac89e59aca8ce3b8dc84cb7bc3d425dbe50c8e59e7c767274
- this leaf
- 2a7578ae09a20a9f3d6b8a2ef0e7f80731d5e6f4f2b4da2ab12aac3d8236e3f1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- O1Ir/TPQVkVDcaIRD42viSyXr/vI6z6OxKyOTMMQ5nIWRNkJxDvHMOxcb9OIHKtKaj23l7YHGCIYzlCkXD7CCA==