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
- f6202e98fdadbe0c20f42adeb32409dbdbfb322d3e72bcb14aaa55313ac60366
- request
- 16a733b6c1cad6b80b1ec507024b4f2a7210891ebb9805b2675233dd6723885d
- transaction
- 353f0c92b0081a75555bcc98b43685598a4e38e0cf62e853dc4fc1e6045732c0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 45218
the chainentry 45218
- sealed to the entry before
- 2d84f5a6c7784ea9d51ebcb3aa7e84c1f20e8cf806577dd211db474a240587e1
- this leaf
- 319b33c86a5ec75e3afc95811115d6773b232412184c73fbc7398faf7e5bdc89
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 1sCNtj29H2l9YqKLZ5cvevGe9NtjNf3ruWLWA6puxasDLaMSsavg4KOp/eA3j/UV6Ah6SygYEQPXliKIHBVmAw==