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
- d53257624a9dd6a84052adba2941923ab67ee8698d2f1e1897a135b3e4473250
- request
- acc11b55523706510190672f2a11f3f57d6770d064f481af2da6a233ee15947f
- transaction
- 09c110baf4e3f5e7aa313edcc14ee5419944c38245c540cc5af9f7b506565e3acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 3794
the chainentry 3794
- sealed to the entry before
- 5ec6aa6b07b6248fa151fc30e22f6c62ac7e825b2857717fe3c2ed0c778cf921
- this leaf
- 021e3a91ee63b886eda4dbdccc5ccb811647d111e402a929971d7053788f787e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- YfzNIfHhzOOiNJWimOpRTA2JCd3gbgZ7wETN3R1PHlgTPY0wKoqJCEy9EG0o0ROFqSJ4vdeuD/1tH+vB1byHBg==