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
- 43377dc11421196930afec5e7019e16bd9db84dc73c787cc286655e6c5f39047
- request
- fdd7ab76edda8427137de9d05434573625482a1652007632cdb4ff0c7b91243b
- transaction
- 9b4a19100f8f70c3cad77c5a82e728967ec5f79b5ccb92b22ad09056fbea2d47computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 43560
the chainentry 43560
- sealed to the entry before
- 3ce04aca5fb13d2139bac16e1f43b9e121d0b3dd39478496907249f8ea572da8
- this leaf
- a29992e1b976e656714dc6ed26d6d26a379183ab36328a55abef67fd5b542d80
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- DX1K/oqmUyoh+Mab2DR6GymjHxCnURVlXRH9PJJDtxRp+sey5w1FXPUE57WYDMq4244WmrJxPOXYYxaQn+D+Dg==