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
- cd6a3f73b26298eceb7d91b01d1c31f7ba758578f9e10d8ef782a36e7e19a59b
- request
- e738f40587b53e406eb2c266e0d971245407ba9e882f5a13737ffd5afd7adbad
- transaction
- 3064c2ea313656bcaf1cdc1e5b746a892d859b158a9db0152078316653085b82computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 33552
the chainentry 33552
- sealed to the entry before
- 5531f6892ce28b0dd636007d34b9346d775393220fe8d523d04d3f872d671273
- this leaf
- b60837543e7a57f16a91d8d0d73f0c3fdad5296365eadec9ce648b502403f534
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- CFsz+1FVEjl2VOIFcmw9+mb+hOZIW0iEk4YriyXYhRjlNJlWZXqkuHuCxi/gH8kd0ykEerFmXv+b8LcM99wnDg==