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
- 31d723ff42f6add59e751f5b9e21e05ecaf849193db48f696ac7553ce1710b3d
- request
- e96dc5e7c4498f6bd5af16b6c8b576c302b49984b7e436841f2877af90b10172
- transaction
- 0a92c0ce004f52029afd8c16ae210c9b791179e682ce137d8445b1ea0b90ddb4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 53923
the chainentry 53923
- sealed to the entry before
- f8d6929d769ccd0788f2343c29c57cd09058b50a44f614c48c5baa76f39f8abc
- this leaf
- 47a3a304f2fbbaf3e80645bc68c9335e22c916debd71ab5990a61e738d61867b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- fMjt3aU3mXnSTeFrnm1C6Vq/kFoYL3AipU577N2D8rjtGjs/JRjrv8/vMxxp7aaHiP2PpeH3SoB6t8SdjVqhAg==