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
- a937c11fe560a26bc4c7b3c1495c243d77d2cdd84a3593d69128c5fbcb335915
- request
- 10784edc2a117b4e1678347058b35f351c23929739909a030651cd18a4e03b49
- transaction
- ca176600aead70e1471152ea995dbadf6118c8ddf1f776883e736e1f399b348fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 32198
the chainentry 32198
- sealed to the entry before
- fa25c90dde04cf853d51fc8b55a629458efc928fdc25575898b3a406fa4296de
- this leaf
- 3e07a5efb8cf489229381f04f314ac27467b56f88e57da44fefeb3788aaf9cc6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 5aR0yUdKke2afzWW3lVz0fAWIlTzhfdDDsHOo97E/xoY/q5RMf99Txe46Po2ZNWsZmYs1LWolIRU9wkoLDf9BQ==