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
- 3ea68fea8dda44396c719ddce053d5c00b8cc4f708f4642a90faca989c816826
- request
- 36538e00e177c17c5f90575972b63e100358e133244785a42969100729db16b0
- transaction
- 536fab3091a25c435afee50836da50c7c93df676960e39472926927984241b4acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70725
the chainentry 70725
- sealed to the entry before
- 7785763d6aa9876ca39f081fa523a9ad4ee91b0c72f964d6457fa606bf4da2db
- this leaf
- b49596151372c21009f6fb7ed877b7466e83d5ac8a54dd50238f2b5c67f7aa41
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- N+kA2m+p65QYevSCMRYwYTDPodNDv5D18AWVL3tgcCVKfsKxebxvwgSGcqc8VzJ3ZJ4OZboYrWKVo7ixE5jiAA==