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
- e11e77c029169d0628013171cf5dc57d590ffd844dd9304c448b4df2245d75ba
- request
- cd6348a8f8a1139e91aeedd178c0708f4e376851dc6bcea157618d1eb0514a14
- transaction
- 406d1233122067d387f8499371b7be6e3c876bdbcfc50df87035d11811d9fb36computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 43188
the chainentry 43188
- sealed to the entry before
- 085b426706756866ea50351faffe07a585de807f4e33c30c8b1f8cd53e54e9fb
- this leaf
- 58081eb410a4f78ca2a2a3d9d06cadaff9e673831f250cb811b867be819e2353
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 5MlGZJv+xqHmOa9fvTRmWlNEq1SdkWYx/Vsr3DW/aIuwyb9aFXIqE0vYej0T6AyeOOK3oQEdSM7oKpaSYbilAg==