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
- 8b71146575b556b0a018b410d8fc1087f962c6cb2295673f88c64e158dcd91c2
- request
- 530a2fbbf0ebfe0195b515f698971fe3e6c6a9cbae8bc0274064415963c30c20
- transaction
- 091c8fa6a5a1043802a5da87d04d753dd9b3ec7db101237266818fec43fbf793computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 25129
the chainentry 25129
- sealed to the entry before
- e9cac5f45b269c15084a04272e04a2a72445d7a456aa1e1bacef833da44d5d1f
- this leaf
- ccfbdd11e3c36203bc7bded3f8fd74961aa8e77de4ce85683d1ed1bab12372b3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- c7heZfnyN++g0JBCZa+kf9d+4bCIASK81LvLipSkHrgNy8O5sivw8uesaCVVNcza/hXmvEzjsU3M5fFgJjdQDA==