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
- 18c39f9226c77e60ff6536cdd94bdaedd27fa20527ffc0fcc6887ff63b2bfb92
- request
- 07d87aa63802d193b374ddc3421f80f685bb112153dcddcf3aba63eb9e2a94ba
- transaction
- 2958f27fe05e8a565f2212039587a924ef6242ccd06de0bfeb8299b3a8b56517computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 58051
the chainentry 58051
- sealed to the entry before
- 1b2f877bf2032d41b654336155ea6f7e952d11e3974d0dfb111e9537803c7c44
- this leaf
- e44be07dd6ad9606f08ac05afdc4072e0b4b10ee4edcd77343104355ba041212
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 5tepCOhdEaAaDhPyoGGiEAvcoXclLLzS0JHkQVXBZDCwXvYqyELvRiSD813BE10qfT6G7ImgW4Mqk+5LU72dCw==