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
- b7ba9324861d1aeb02244627a55a1d854d5c9cf582a72a286af6d5d1eebe74b5
- request
- 1c95b86f3d27e6f36aa1bd81542b72d902fa88fd2287d70875b3dfa5ae3cb937
- transaction
- 1fefe5e1645d872fa8c95b8b8e3f1ca2dd7ca3e76a930ff2de37f561dd34007ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 38104
the chainentry 38104
- sealed to the entry before
- 4683c00adc2eb9f92d6ca1f449ec44ba95c5c1fdf571559eddfd0da29696686e
- this leaf
- 40dca3255919eb8fc82cb7c13ce9cbf43c798c7eac44dc1331f10d347aa5d23b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- XU59It0GcTbA3LS2BUIbScia6dN0RDK9u1KkF7GZnNP1N2JRMRFluSq5vMom3nf7g66scaqfZc8DY8HLDKJADg==