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
- c7dcf4265f128ccbff413144f3607f99d36bd21d8923745d8cd67f31ed8fe6d9
- request
- e12f3b3ba7474323bb7fc924255f140cad19acfbe0b7bf6641a3f6c8b302d5e1
- transaction
- 10a2edb33d5ce3b3c06dc6503a2b79da758b1859b4e319d8309488ec1bea287ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 10032
the chainentry 10032
- sealed to the entry before
- b5ae14c3c8024828a1f3602198735ee807945fc9c1f6fa78bb5c35d176658afb
- this leaf
- 935e26e857e6d1ddf0222825e1274d4b61fcb5a34dc60d2c5f62e67f12b0388a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- mrXuYzqwfg3PVniSZYHOhXMFZnu6L/DguWH+eC0VCL+qedKO2QhfttCoJCryZhf1yEQ9uOww7r56YYRolPCDBA==