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
- 4f11b274f475fffc10cdc6330bf24e949f6fb53c577542131ec45002f52b3e61
- request
- 8cbf8afe709e0c558834143950fbbfe74778f92b99310e6cd0acc89bf6d9f0fc
- transaction
- f1992966483653bc41c04fec378aa8def13097d7bc6afe98f1e0f7af90619e2dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 45836
the chainentry 45836
- sealed to the entry before
- d808896eb735a43beba40058b7883bf46215552e16d5bbcd795b02ef60bfcd61
- this leaf
- 01c01649cbb40d4f350d281b25b3ea454baa69f796cb8847845c561a8fdd3d9e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- xYF3IkPwZbSutOTcPxIfd3qinIRtbEG0bWfGA1UfN0FBNmgrV8fDVh9THaoP5kbC8uCdEd4a71ETIddFrMx9BA==