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
- a69d05f2a11deee3989f130b5b36fd8a6203cb2fe204abea5f0823f4c2b1c4b0
- request
- 17685e8fd5894aff8f5ce9491db822800c2086756e23e47d752835a6bd341466
- transaction
- 83e8bf10db0907c8fec6358c16ce7b03a57398de188c3ab89874355ad2634f78computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1850
the chainentry 1850
- sealed to the entry before
- add28f1a58ab9b48ccee7c42c004f35b6471d6cafd1420dae73fc6d1e51dc3aa
- this leaf
- 95945f381d1aec22d74a14a5d2097e484ccc749437f520dcb3d06d8cfc04f736
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- aW/t+PG4d8lyvC0uFfYwxFPJhcqKZ7UCOYwDlXbqU80W4TW2z/+KemvHJ55d5GNTkrbc3W6rvS2wabcLXTzmCA==