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
- fb690aadb06f8cde378c416b459484991f661aafdda553d7b46d79ab90eb4f65
- request
- 6642bfc95ede4dae8b83149e50d4b244976cf569df36c9515706f06d6765f9be
- transaction
- be5268d8fafad6a0a601bc0e425c2277965359f58619a41d38089aff3d0438b1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 18017
the chainentry 18017
- sealed to the entry before
- 91981582be793bcc0dcec5e19bd1917a1ad2ef37049f21767d40cfd12b47ff26
- this leaf
- 0d474af964f319f11bf1c97bf8e4c0640654dc9e264349314bd2fbe0a3b6425d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- RzRO0hr5Mi/VP3TYg1MtogwV+lJSVh+Z+tKsGBFtJSI+608977Z2fujVTXZB+ECg0MLMQhxyY2NIGMnpURyIDA==