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
- b536a07d9f7b707a3ff6dd1f57d1c3908cd346fb7fa17cedfad320aac4ad95c2
- request
- a3f9af77328c6e5a7da4a06af123cbf756dde20a616a39fec1ac8e0a7e4b3b52
- transaction
- 3be1bb0bf74c98b3ab892df9cdd7b2d762d8b4cc75e95dbbc47d6a7044a01394computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 49243
the chainentry 49243
- sealed to the entry before
- 3d8e47efdc3fc73210059bcc4fba8695d1b9c6ef1e24610180410c7ddb3881f0
- this leaf
- 745bb1bb1f6a1ad27337e4ce8e0f79afaf4848b6627b0e4bfb4ac23edcab0304
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- cHyGSg6EVtkpthikHpEO6Vw6Juqeg3cpy8fJOByNWfVZ7moN6cjG6SPqx6uMg64KBcCmWRay9voHAOjNMIZrDA==