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
- d93601823a2048ed46fe7ff2e1a12458c112a4988da8d40ada1c54ee46142774
- request
- 20d5394a0851521729aedde412e346a7ce5c26e71d495dbee72cf01208445901
- transaction
- 73450643b6c59470168991a2a24e785a5a16d8d68ea1d05a308c12baccb13ee3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 746
the chainentry 746
- sealed to the entry before
- 62fe173d279fc85e37fdd6260e857ac94e67f5621abfb772f848fcb0db8cc199
- this leaf
- 50c90c209c3a9f9079afc86545b74179db44ed9e8fd7fc77b10dd73ecb65a286
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- xVwBqXo46jNEVYoRojK6gf5puPWkYntpUvVrxtufD0quwjrk1bpFd6+35JQVQN72xzrvjQCz+0afMp2E0QHmCg==