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
- 85e7b258171ba2db88b5ef9c02807ad6d0968dc7deb4f3b2db77b95cb35461fc
- request
- 6f2a07893863f85c80209dd84093d0c2809d35e7721dcb3a8778c6fe36bbbd94
- transaction
- 0f8a01bdec23459cf0b7cdee169795efe8282593252ac31a6c9450b9564034cdcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 61935
the chainentry 61935
- sealed to the entry before
- 72c52a620e68da53405ccdd763b1dd0c1e34b057fef8aa7ef4cb23d3110e6a8c
- this leaf
- 3c503686843e35c15d901f4bac51c7e5bb4a6dea254257c8366b5d26c3d0bacb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- s1FttX+nFwu+om9ps79/8Q8Eqk9Ff6fc2wV8kQR9QUX4ivDhPVPAX/sPgJp50B07Yd3vNeEmRuAec2iulBXGDg==