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
- cd9c50348bbe77696c9a308c58f074eb62303163cd28903027659ade263c9228
- request
- 78b4db02b7c5610f293bce66f51b9b03343a5eee3cd77bbe08ec1e6d72dbd986
- transaction
- 8c9f793ad9f193437d0b0e69b217e9e889aa595d1738a5a35b48c5cb143e50cacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 63740
the chainentry 63740
- sealed to the entry before
- ca8b2e5f9c33ad9a01912373d7555e20ff3e6f747d7f284797ae38653176678e
- this leaf
- b5852d32f05a695bf4bad3ca444bc03942dcb05d0215c4e6073d3cbc88249edd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- XsAcaOVexYwYzADBAfSqAFtqWz1Fnvxo7DWvF0ORIJMI/dq9Pw0Bwlk1cHs48bFlfRvMSWnJjuORgFRXE2fCAg==