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
- 49f9fe23ad19ceed9a46532706c76e05ac8ac343d3f482b114d90eaf96f44393
- request
- 616233cd66641e03c216a0af21e8bb7d23f67ec99d0addc4c02d411c8a771453
- transaction
- 0f80204d64eced3de44ff8b30de9ad87d08ef228347a76a90b523fa098d9e278computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 34035
the chainentry 34035
- sealed to the entry before
- e4f8c2a706fee38b2d6c44cfda1db0cb72ef6d1f6d14a295dca52e176c199e53
- this leaf
- d878632508e756908fecde6afecdd89398180e1b3cdce26c72f2bc764a58fffe
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Y2sRu2G+n9Y0KdtggpOgCKL2GPXaAbkUBKvmv502Y1DueV1nK34E/QuFzniGcZI54CdNbHy2N43wfvc+wg63DQ==