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
- 66b33807c8af31a70dd874ea2350cd81aa24d24da2e577f7f014ee5a64e10a72
- request
- c1ca5937edb39bc5082ec5a21f599c58a583f22988084f0b23aafe85db8e0c12
- transaction
- fa3de1592ec2cc25f1469a5b260770206e6baf1c6aafb038c7ce6883066d5cd8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 58205
the chainentry 58205
- sealed to the entry before
- 0a2939c8f36f7bbbf10bbc1aa18ef796a21dd88da318d5c9af3460bd0e059906
- this leaf
- 22983907fc2daa3bc743e917ef56fa58bd0d806f503891bbab4b877cbb4da2af
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- lNZQMt1Ifl6E5la1CGWCwAaZZH7zspntsFiMpRCzej3X676LVXryaknIweypEXWYX+zAPgF1a9f/5Q7YCri/Aw==