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
- 736332aae3d373c7224ee78c63ce4b9455ad02848b25c49248ff1ced8b71916b
- request
- e5bc61ae32b8055eac1c1dddbfb92129e27716c2922e28c2b7421419ad46c305
- transaction
- 24c204b5fee25c35f939cea44b0d6589ecb895bba470a7fd456910088535d0edcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36315
the chainentry 36315
- sealed to the entry before
- 00bc2c4ac2cbf358311a38ab37078f952d9dfd2a22365bf6178ede096e87ee8c
- this leaf
- 0cce9918400e9245701552cf98b5fa79ea80e8be67ddc22851923500bb5c050d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- YekMNE7HuamFzuCPPlF3adMqGV9cKasaKOmJQAuCenChJmQMq3gpaz1UHADYVj0xdW03G43ZtVZNZs+lIu1UCw==