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
- 6b1355b33d102cfc7b505273375bfe41fe7e9b309023177a171227901b5a6bbc
- request
- 4be2d61a55bf8708faf92134c989adfaa5cf0236bb31328b5e361a3353244616
- transaction
- d34041e8dbcfd1c75606ba851b59c6cfc1f8606404118ddc406ce6f768b41426computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 65691
the chainentry 65691
- sealed to the entry before
- 63c5b397972dab36ee00ae42c327b827504f266b61e8a01d0dbc8695a0cef5e0
- this leaf
- 25e2919e6d7ee04118335a1884e3d835ee23d00ecdcd37ce5e1176c4c27612f9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- I/Vuh2EOQ58UNrabhRaTvs8SZRkxT7BykmCE76FDXLCtxxvT+Vf1jn2EN5dbYVbPjfHwBLR7YNgyHy2C5SV2Ag==