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
- d690d8018e9822b678fa0e455080eac2a432a3ffce3bc009aa18023c60d524ba
- request
- d9cf8e3fe4957755962aa835ef91454589eee1cc5745a5790063c05af1c1787b
- transaction
- 5e619449d4d7d28b41972d51925fbc6a4a8a824cd8aba8fc150d66d0715c7e6ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 38499
the chainentry 38499
- sealed to the entry before
- bcfc3d6eac4c51eb004b4a71e9d71a3698a18dd5b3712b3b66dee6b245e7eef9
- this leaf
- 911bd8c0adc4e871d4009780d48c011244ab35ac0e02fdb5ab69de71cab0e109
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- UL0qOYExXdz7rh6/iwSn9B/GaR8i6pSt3CFOQIYXVM5c83lnPTTU3TDQ2YJMvNJf0v66oBckxfCey6w7K5gjDQ==