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
- ae7cbab3f28e564ee1b8c4152be3502beae16f5f9da33b606f3d902c76cf0fc7
- request
- d6babf57cf1b08afad6f52cb5632710cd64b4a3ebcf3bcfab39bfcc9bee421d7
- transaction
- 8721780589ca9f28a864800e5d9098dc9856506890108e4840e06ac490217460computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 15440
the chainentry 15440
- sealed to the entry before
- 3bc75afb93185a301928b8946e7798aedb84a3b6389b4c25f63b3554d1150bbb
- this leaf
- 2ff6567aee89f1464dd8e7a2a47213f6e52d2d2fd9dc7eea3cb5545e8de8ac0d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Sft4ahtJURCYuDySUVnwwEg3Nd39HLDmDEs41bZKoM83exrxVkA0v7YTps1/SqrgKTBgwbO6FvNuIGnV7pksDA==