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
- 45288e463676b84584651591cbe2d6a42e345a335cdb2e7fd3755b894e6533c2
- request
- 232c52a6ea02328d74c1515be1d14bfd1d8ae2bf08aedc413d367c68f85bba87
- transaction
- 8e049f7447afad96e20639dfd32a337503df795b09f06f7be3e78fe1f8540596computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 74733
the chainentry 74733
- sealed to the entry before
- 656b29ee0d9ee2e73a2c2f37a696651c4fa0bc8e0da471077493e21908e2a9b6
- this leaf
- a84d879680bcc66db47024af2544188812e6fab79368aa2dafae010d8cc1d734
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Ts/WdzKSfIebUsOnS1Xn3fQwPjEhWrCdP2aoWM4OtE2e/TaaCDQrpUCvaNNP4Q8XpPB1UydE/vFput631cAbCQ==