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
- 1b367b0282dbadfcefa6e16a38838dd3fa4afd1ed7025d66c28fd7915f52f473
- request
- 4561297d356249b2e83131b172779ba67cc387b17d3780589b563a3b06a4e7d0
- transaction
- 7f87bbc76bce233a0ea797f840c1f243c8428005229ff37c49945b0cd4073c21computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 39626
the chainentry 39626
- sealed to the entry before
- 1eecbec66e3df737a2101eba8e6a79f7c0eb6e48490972545124a36468db55b3
- this leaf
- c1f8c244a3d68c1b189c7643eb9b417fa394062884db6ca43b2f92459690ad75
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- K7VAZnZ9IaVae3pu+rLX3I5uBm0VzYmEGadFrkDcu+Ll/aMg6Ddfke6yEGj/xXQl9RY5vtAoNR6M3NPWhOqdAw==