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
- ef87ae70ddd267c428cde98db7dd0a2971a056998d915b323c64df2cdba2392a
- request
- 6c3d304fad301cad75f225699c296e750cac0337fdd955d750b36468c5857a62
- transaction
- 512dc52e8e16375abfd08f63bddbe439a94c67377ba617269a8938573072d95dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 17792
the chainentry 17792
- sealed to the entry before
- c1e19ad6e158bf48c7eb68a8b67442bf01d4d2cd8761a6f9eb7db85c62fb3f43
- this leaf
- ae1f1d792e179e28872fd86d9fc9fa856736fdab7edab76300a79b7ff2b66003
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- XaxdfqtJzR4OVAq8dfZ9+j3kQ55YhsAEyhGrP7SF549Lk6pffH00Fgsyuwh80EAtPx9rbAX1atYcSk75eprUBA==