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
- c530ccb7973d5ed09300a2ffbe639576be6dae10e9ccc8e6a6ccb79d261e2149
- request
- 46939e6b87bc67aeb6e9022fbb8d3762c08fe0ebf51d75ab840d680e75700278
- transaction
- 5c3e794b17ea743b689e83a238c1201b0f64de8e0ac9e5c869975c6660747f7fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 44306
the chainentry 44306
- sealed to the entry before
- 198bc8f9c4c5cc4e7ac311d0773b083fb365571f13ba5e207f5083c15a39a68f
- this leaf
- 53f7429de57c9b3d98a33f559f2e467db5cfad936243f0ef3df2912acb0bdd3a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- VJQc6gP2gBUUIgQhl8E6QYNXtTKvVxD2Eur5z2vuthQ498cBn16L4g77qdbm4W8E7uw/fPxYijd9db690G4nBw==