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
- 8d3a3b22a551db303692b39a7bf40970fe533f9907fb7a85c4e80904b2eb47ef
- request
- 37c8a170b2b8f689e062d97b88d7b1698530336eed402736eb692a93bde2ac7a
- transaction
- e9946331f84888825c3306bbaf18e20a8a1a7d30f69f440ce375b0972ebf77cecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 39688
the chainentry 39688
- sealed to the entry before
- c93c021a8dc4e65a3c6f840c543bb1aed19ca0617dcf4aa0ebe5d457cdac260c
- this leaf
- dcc73c4c5c6e038f8007878b9066a80fa293e9db6de361188d7c96bab7d4c185
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- MnOYkIhIGw9c7LKa04OYDfg3F6lnDZx3t8d5G0nTxOQim961dgWU0MbZQPUaJpi5AfY3tnNjrdMeboxSQ7cDCQ==