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
- abeb2054f2bdaf10a6485af3a23847eef65e79374e8e5b89429f025605584a9f
- request
- 2101bbb4c253232735d54f2868acba3e842fec613e656fc922417172503f4702
- transaction
- 8ae1d7fe2f27babdf74797d7d92344a050e04a36879b325c1a3b73e9cb3a6cb7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 9153
the chainentry 9153
- sealed to the entry before
- 6273221389310d1c7c6a9483c91444812a89c39051f2f707e813edd2a7fac4ff
- this leaf
- e4fc720fe8aad75660d68f3b547464e6950950a1ed9288738666559712dbc7be
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- d5ZkO4lOmIPPomqHMmRP7RXNMThXXDVi7dN/AyfoiXHwhKyz5QMPhAtUnpG6dDUT+zDVXsFUoXMahhyX63N2Dw==