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
- acfff03f609151547a3fc15fa08a95e702f4b58ce529adb27e06f1fde52b6970
- request
- 392f11b861eec5301fc9527290928b1875c05e1349fab540186bcff662fc15b8
- transaction
- e852f6936c35cf7eaa94f56b945a59820d152a22aa66b62d81df92a9b1deecd4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20299
the chainentry 20299
- sealed to the entry before
- 8ded5d20411d20de8d6586cff2b687ca048f0aeb08b2b439acfc713b7b964c3d
- this leaf
- 30006bbba000d7519923d728dd4b31a2fe49b99cf5d49c02eb53496dd0815624
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- QcQ9xUWYb708OuaRWXuF8WhLVEIhRVEqHQNgMb1uI2aaVy/iyqFqr0FzhO5U7q6dBc1jcGX7ZnBpcpevUlM3Aw==