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
- d65a1122d23985264376359c914c1dc7425192f4e795cb41e9365044c96aadcb
- request
- 4c982aaf3f9ae4357d8b751874b3a7f0e02a82982e2933b52eb4056972018401
- transaction
- ec3dafc140213e6db2ffb30bf935b9390782b4261554f9386dca7bd88ec22993computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 77123
the chainentry 77123
- sealed to the entry before
- ca5f8d2fc915d045f164c962abb9a4c69f6deea3c57109bc1f1ffa408a19701f
- this leaf
- ed89d162d85c7d996ae99b3837689e4c4a9edf957febdfc5e8d6a965dedd1698
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 9hnolBc/pB5UHdzFLo9NEnZY/xjBMbu9v/9NA40AaXiaUBpqcJjN0pcy/sNj0u24eQuxJJN+CU9qZrq1AvxvDA==