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
- a2380cfec44c487a834f40541b2bf09cd73216ae4b037b0bd5ab1c187db74766
- request
- edac1b6dc80ff169de5611b51e51a658c5e592a59d9184c632aeab9eeb569e86
- transaction
- 5685650f6c8c3358ac761d12ae4b1665e553d96fef0c0995df680d1a24157a29computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1855
the chainentry 1855
- sealed to the entry before
- 00931df492dc97b2b75b3025598d7265d56086a48d7b46666ad4d6730946a72c
- this leaf
- 230e596f2484c127dd6d68731e8d664f60b8e7b3cb4f409abf2c47ee6862134a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- CMx71gbEH7EzMcuAnR3CSisorE8PeNqLYGUJZyUaR2ttV7p/2RwrYbdWzJ4AuyMRLSUQRbiHIj2RpVuM4pquDg==