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
- 4ea4f2bb64ea3b5dcee76f42df287bc696d49e4c7fe37cb6f1fdefbf79774e04
- request
- aec9df5535a1d110159a645d3be1c304718db995c85516f3503b4504ec9b6a74
- transaction
- b9eed4598deca58df0e96d306411d15d79a88fba15992263e9e6c4471dbae3e2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30250
the chainentry 30250
- sealed to the entry before
- d600f7ccfc424e25328d6534f66f16f18abfdb366942f73e909fe0d4166b39e6
- this leaf
- 972d921809fc6e6a63ff1aaca93899640fc85555faadb78e5fa4f9dc5bd42023
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- htrCA3qTA/RmiHqoGIKKkgjvRUrqi5R7UGx/LJkV4P4yt4HdhVmCP3aMRrEt15koRBwh5lNO9rDDSAhtFT+PDA==