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
- b9ce69710c86a12b28de7c8445c4f8685051d87cc6c7cfc75c5cf6569c279d1a
- request
- e0cbd381b1964f94a870d5ed037a91316e1316e47ea2ba890303b5a19183866f
- transaction
- a6a598b18178a2088c1ab646bfe78c1e160603228f596e968120b5b14a75c57ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 34877
the chainentry 34877
- sealed to the entry before
- efac188a1ec9e40427aa430ab48af972f0e25c75a7fcb5c1a5c3b2944aa20592
- this leaf
- 0e7ce545194156172712e58b9c858e9760fed658a3cb97772f2e0cc7786a1b2b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Uc/BjvbrnVB6p2r3flV0itdEB5tn/iWfOBVoCaqasNqq7x4XiQm6wTMg8R6ZAlamjEPNVKVUxbqUJHjWvJBgDQ==