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
- 3a85364bd08c7d1d43913fbcb6a7bcc2786f273378f05bbddba39130c34b7a6e
- request
- 11a9d0fe5bc29b707315ac7db2f9a3fc03796e6906b2ab4364b5cb0dbb21112d
- transaction
- 9ea59f5c08e93c4e723278905366d8f382fc90435a0d7ee97c12fbc9c4033229computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 3449
the chainentry 3449
- sealed to the entry before
- 1cf8bed5d3842c727a570a34b5293e5e5771e7d56c361d39963190b929f8b4e9
- this leaf
- 4c44e88530052c4e4e1b970094ea3290d978af09d16958680073b7482621d9ab
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- G6qDcUQgzj7aMeS1oHS+6pYyAO2o+OzYACJtn1eBye2Tq4WobwoyfbO9YhR4WVdxzKgODEkbCUKsAkcacORgDg==