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
- bd7c2384c8bf817846ffc3b4250dc64f480a2f44c5af557c00f3c954eceaf88d
- request
- d82c047235bb10a586beb0b748d4edefd58e3a4c272bdc21e61390dfbb7491e6
- transaction
- c3638acffc00ab4762600d1605ef825ad22450ab3b863e9430ea54d33080380ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 25348
the chainentry 25348
- sealed to the entry before
- 9174ab694d40f3166dd059a8e4c10aa95e249667021e88b04c8d83e909755332
- this leaf
- d326057dbde1cc3b91fcf6bc67f11b12cc8d7e3bcd9a2aa398276183b813690b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- FBbadoR+S9rMzEA96fj2dNatA1Ceueu1GL45EWvCBYO1B6uayZClMt8cmzXIXBNP9GEmtlkIjAQu91ZpJmB8BA==