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
- 1539216bb1b1f94bff7a2e7d09482a250a8ff7251a0a18eab3796f0c6ba15033
- request
- b67da903cf50a6611a929e45869c969f55bbaacb5527ac44b4a461ec70e95038
- transaction
- e58d67260d0864107756d238d46a9d529bf2928c53785590b3bc69d47937cb67computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 44394
the chainentry 44394
- sealed to the entry before
- 6a50867c75446e9d9960fd8bf14b87eb714006d6a79ae0c5fa7c2b5889d0e07b
- this leaf
- 5bbac20bc68b9256b956323faa28588a87a65ae66c8458f095acddd5c6c03efc
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Nzir7v42SNd0vttQFA5xRnbutWE2c4GvkLg2qgfVcCH4aQFRc1rImO27VJDa+JFHibCcsHTGzGlxgs8YYIF1Bg==