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
- af45de7b81828235b4c8a7525380b5d9601bab34eb57dfc25d9cd59f8375923a
- request
- a60c7fdb456868d14c820f87802691d87a4be6528b051ff61ba0719c0d08ccee
- transaction
- 4be0c846f88227592dc93abc537395c786f5d4963137b278eb7b48074a492908computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 77272
the chainentry 77272
- sealed to the entry before
- d7baae3ccfd4b4fdbb9e81787f8eb34f967761b7dcb364b4ce56ceea820f4794
- this leaf
- 14e169caac1691b0ef86226c45156e79291995ead72ed2804fad1a23f1ec26b0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Vy18RbPFNK9+qgeyadPCPBYNLD1mO/yr1V3pWprOGSSjSI+CqS32HIdrFu+HGidk+YVgRT5LTcLlifR2m1kNAw==