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
- 1afc6881211d7e286a91c83bc11156af3572bb0e4890f18715bea96b6ef578f1
- request
- b421b6f87194d81dbb5a1cfb2ecbbbda57df6a4f115207bd5d9ac4f2b80c30ab
- transaction
- 92e63b49ce21d38f941ef5115566118ee0aecb5eff43eb08f6033936e43f5c9ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 10418
the chainentry 10418
- sealed to the entry before
- cd5436d280caa4556fad834b6923033564735da208578d17f03a2adf047309d9
- this leaf
- e97333cf862c91f03907c29f83816a7ecc048093c429df3396fb18b0b5c48b3d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Oa0Gyv35oXlGIb/GdeMjNWCFC2LeWIK6v3eB8LzjFuxV4cphywriwfJ9E010E7vQ/QEmelUe7SdmmUX+VGWTBQ==