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
- 670033c6e0db6926a648616f68a72c673cd7691d7026a924e37721bd20d66b5d
- request
- 46c250461bc0fb03e28dfcdbcd859103ce591f3e6d1cd232512e1a55b4160c52
- transaction
- 889ad2fe653f389a29596bed96907672a0dc9f1cfe2cbd71a30d061ea2000162computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 11722
the chainentry 11722
- sealed to the entry before
- 44326868ef1d391a082a4add95a9e251e93f514f674152a836762872125ffe55
- this leaf
- 6a8ef303a643f01692906cee712bf066a3cf9220f4252f83b2475f5419083143
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ZJOjJ/Tn3Yk1381rCD1WwSWkO7IRaVLXrb9fMlbUCYESEKknAtLyLSJCO9AWTuzx3XnPooXSFXV+daAFyqxKDQ==