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
- 1059a59878d1dbf95c36bcd3b4f48255f236233d5cd1205e8661acc63bfe34b1
- request
- 98d4bc75b3f6dbcbbfda08d3ea4ad6584ff2e51c3d519d61547241e06a2598a9
- transaction
- 34386aed9bc4900ae86735bee1eb2de2373d3d2d78334b47b15bf55c1642ec93computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 17631
the chainentry 17631
- sealed to the entry before
- 9791bab4abf45eb8c6ba974622e303995f32eadddbd24a8735819ee70048af91
- this leaf
- 89627133cc12934373c4d9dd413090214e8f8a9fce62a8825bae82df71fc3bb5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 7iDpHpjXeGKNhMdee0JS3N+C3/PLczWsEDzFfOb1eQIKIMuTqHjbpYR8AqIbFH+ijoK7sQLNXDIBIe49DDRtBQ==