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
- e63388cc384f2c43be8f792c2cb8757c56e12f68f4f9c408a2574a161c4cd092
- request
- 0d283da5777e94c9c2d3517a405fa3d0fed965c6af0f8d7cf10a43e6ffc01faf
- transaction
- 51d04a9f8e2af70922eb30931e473a2e00da78ee0abc9cd7b4399ec68a2f8ec1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 19714
the chainentry 19714
- sealed to the entry before
- 0a0a1fecb99d125c5ac13a84bcd6fbec225d12c3bd003d39f712f2c222077cfd
- this leaf
- 26d8abc54df321d30a4c7a7491a67af4797bf2f47dcdc9344e8f0e09fe96d161
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- UVsdouGZWXMtuIraQAEAsQ9lycR8NpNs9IFMPxUELpa9zHFy/KJ1LQFGXRhQKpXnrD+drivGxM1LVzA9fFr1Aw==