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
- b70493a45a557450ddd62f46aa6a861313e1f8166874b24adace673171208a1f
- request
- 0bd855caf0324815f8e2ab80f3edc3cdf7ad6d52049693e0ef745e570f1c9129
- transaction
- f4953a1548ecf76115c8d5b3cd377ea1e0561652015d8fd14875fb89d7f910adcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 14420
the chainentry 14420
- sealed to the entry before
- e6603aff5d66ae97d3a9371c391e11ff5af483869abbb6062d98f74c9d874584
- this leaf
- 6541b59afed9b4a928b2b75c7db161712ff1fc552d03d84483d36a499cd9a791
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- cUqioK7AB7LEFpNo46bicJEa1bBQsFUfpgJHXosTT9GQdTn0oGWEnVHkqt9lv+evRGnqjVZERvtQ0ScG2oegDQ==