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
- 5a135e4080ae1a4a2e6df36dc774f45f3c681a1942ec1f54d0c6f3b49af4b58a
- request
- 7e0fd3ba661a9eef5a1873e774f7bbe184c283ba845a3a4686bea5f1c9417819
- transaction
- 72f3f296bf001ee54082622e9d9e8162da4b4da47e725db90fd461b05c9d5d93computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 76258
the chainentry 76258
- sealed to the entry before
- 64049e3db5d17ef0723c3b355e768e7ba456b7f8123805407f3e15c0574bcda4
- this leaf
- 5eaaf40dd4f2d9911bcbdc9fabd50f2afec59d00d7a21261ed1618fbabc56e75
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- c2q21qh9wUzAfCAuLQR4OCZGqqnqbveuNHI4DfoDT/V8GAqaBLYJr520Xw+6iLVQjH36BEGg87XgAfwkTdd8BQ==