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
- b1da33120355c0fce731005ef0622ca4cb7b4b0fc7581e333dd93f2d019b302e
- request
- d37547d39893b9f5a98f00386b6fd0c6ee72d76a61db9084b09953d926add304
- transaction
- 5a557c3462e180fbc57a598eb26c69f5a617f54f1492421f22b9ab00d62d0b7ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36885
the chainentry 36885
- sealed to the entry before
- 4c3aca08269418fd0a89e2f6fa6ee46f44aab9869c8d5a30703b6c300a7c93ef
- this leaf
- 13cb81798ec8b91f48c361efb18342e22da73e0b8d87dcd47fece6b5ed6afa86
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- vjfDGnnAUKBXdEpRlLKYaWp9C5YU6fZEqe0R03h+FYfQoSwxe7PaMeQv3eINutrQgF8T8lH6JX120/LssZGqAw==