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
- 70ce93e2506711f109bcb3edbbeb1ec72395f8178af32dc39dfb271911689146
- request
- ebb89c3bc255bcfeb972f3d452ec092ca83360787d508f06aa8bbc99bda03d8d
- transaction
- a2b21e93d960f6ad94cd74ea68ad1c46aa09ff601fcadf998b01dfc6dd6a5e98computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 53125
the chainentry 53125
- sealed to the entry before
- c99c907636738090da7dd99d9b36855b181aee6c859d61a34c52c951ac92d5bb
- this leaf
- 3ca0d10a2e358566005c61c4d0a1dfab904f3a74f14f0039a4215d0ef4c1494f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- N8X1bGc2Lcb15asJylrrI05byRql5FAIvsrYoF4l6yPfjqyqGJGc1MsJWKF+Me9Vy4rJ9naWzWfmfd5o7DU6AQ==