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
- 37d5ff236cab449ec3fe3c852c237201ba4055c40ae1d32e78db4fcea3801edd
- request
- 60a20dedfe46b454717169f8e6353e715ae1f6197ce99c7c200ff53163f8db37
- transaction
- dd83a2e8b47854566d4eef45af9d0197978e65ffe017855d879e5609ef2043c5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 25916
the chainentry 25916
- sealed to the entry before
- b15b820a159f7a5ba81efeeb3f80c9ba721947c039f37a865ab3a6bcb84c6637
- this leaf
- 4c8eb1d40241d5eff9ed54b93410c6d531037bdd141cc455817e11314a4e0e2f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- hQc8HLdMbyukwMAr2HbOd1yfhZUgZUazy1ivdXECBGNjdwWdlkagUrvmXbTpe+miOP0BT2BVCKpUkjTNMl8YAg==