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
- 928b6937af42f385c4fcd5476179330cf2ed9fd99a1fcde1ba18997999221006
- request
- 6ee1e32dfbdb3b3559c0941625a610e51a506ab3147d9cd1cd370bafe1c78863
- transaction
- 205392272674b9e8649631dc6271b7c2da7a56160d51878a7b649079b492f873computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 57925
the chainentry 57925
- sealed to the entry before
- e7a2156ad322f860a3d64600fc876d55ad7e1617ce8dfb92da811875f0ed2a34
- this leaf
- eae556febccd1dac1c7eb7ead64089cd90d11b03fa798d716daed8aee3e149ef
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ZKCaV63h8cNpLThdXr60z5N0Ql5W16hLVaAiyNm/7//OnnoapLO5mVJ6DSjynOvAMyhzLNvxdyxhxS3yI1SqCA==