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
- b98c09faed7758f599506f247032d2cac581f10137eef85d14ac0f363dafcb98
- request
- 5e8423ef5a103e39ae87eb3eed12089cb1cfdd5857cb8c7412cecbf8a9cfecc8
- transaction
- 92bf05d1cc41165c57ec96163f6d089acf83de61517f1f1ff8584c8effa1bf56computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62493
the chainentry 62493
- sealed to the entry before
- ff0d88c30ef11ead2a7e2848bb72745b9d919a8b43e05f4723e20d8f1d81b063
- this leaf
- b2f499b35221ea98593e3666c5fb737a9e1a579b196d71fca1d96b46b5258c0d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 4TDGjcR+3rXG3+URQAhSWjJNfEWM5Vbz+M7iMCLQ3wrQJrV3aVJ5IyENpSaCJ2oZRp1EYougVsc7XGJQ+JsSAg==