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
- 0d62d763cf600ee7d8cae350afec299d9623503210f6e87fc35da7485cb92424
- request
- 297bdda68e16ed17be7ca26944c7a1ffce2101cd6f4a8224793330bbb594b5b9
- transaction
- ea6512722ccf502dd460de6fa3c630605fce326fd1451f12d4ba41cc1440de38computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70373
the chainentry 70373
- sealed to the entry before
- 0cd5ec7db51599c39f15c4a5867e5f2c4c36daeb6fa464c7030636cddfd55f28
- this leaf
- 1d3568f17db29bd428b2bbd5eab55749b2bfbaf6134652af59033ff838504f90
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- caFrD7DitJQPlTfPwgEWJgQjvPzFT/HWBv2ByvqFR+lQ8Eo67T2efjbs7KRa4d1Gc5XpIIGioWf/DREx0Rw2AQ==