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
- 8ea308a11aabcbcb0a61f81675ddd664c8b8584eefa1c0077fe6deecbf9738fe
- request
- e23020b8efbf4d5ff21338ceb0d3477b13ad6259a686495b807198691c2404db
- transaction
- a0a506ffe39b99b35d8152c39b9ba55170a916c3b39689e46ef7216c96d64054computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2210
the chainentry 2210
- sealed to the entry before
- 4b92d7a5e455e169a30af3c51bab1ade9cf2c803923557e62c7bed9a4d936252
- this leaf
- fc3904722aa173b6eec160f6d125ed8262ee6be2ec0f2681fe86750fc7e4a47f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- KWPIjGRG8aXS22pSgGI4MNhbO/cSj2+YINZ1z4knwSGJFo/1OACrOOy+85aQRMh5O3ygL8ei3IF4bqcx7x7VBQ==