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
- 08f9c3220775cdae4fd236a5d3071aa714b21bbbf17c3ef051f41a8e4ec03590
- request
- 3a9dbd0a9acd6762b40ec3547e222f1626e400633c6ae2ce2af92738a6424dd8
- transaction
- 0cd1918673d4913ebd83c3d64c53bd079f8a726a4baf100a53f1868919fc13cdcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 41448
the chainentry 41448
- sealed to the entry before
- 238d0973c7f3df930ed5af7cd6432700a29a9b7ff7796e29a5aa29bb4b53dfb9
- this leaf
- 268d84134bec724227e9bd3a5b4bdbee8bc7233f46ea230ef7a7da03c1f52dcd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- I3F7YBjR/2tqhI06Y1KhcQ0MHX4AHUpzKe15HvfEPAa/UcvZ2S/ZlG6upqKKTbwmd3SJVGKbOem71k/nIMLSCg==