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
- 75b471a92b86cd3f5033321d815479097708304a6fa423d7e63b2ec8cfa174ee
- request
- b083d5a624896bf2561a00a78cef808251465968d47338d98a1be79f9b96f315
- transaction
- 073ede8a360997dbbd7e8c78bf7e7ffcab9937aaefd150397faa3c0b669ad441computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 72519
the chainentry 72519
- sealed to the entry before
- a4ca20212dc3ebfb4a039bdfb5fb380a48fb6ca47edbf8562203afd8e3aae187
- this leaf
- 08c29eded013155169cc3786648f5d8a99af7bdebdcc958c8cc96fcd654809a8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- g70MW6ii08+WoVHy8TIJmSGLt/w4O7GwWTsUbupXeGuPf+f54PVSjzowdNu8NupxKi6BlDIS3iCyS5v7brMRCA==