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
- b63059037e80e7d5e924b14bb330ce630ce89f580da2b59a7205f0b0448eb1ef
- request
- 8ce536289bd19fdcd1d27d04c6a5c4f2810cbabeb982c7533592a73f8528d518
- transaction
- ef8aaa0ecaff3309809e8a7b6ccf6251e4002577a5d2f7a7d02968c36f144d2bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 66730
the chainentry 66730
- sealed to the entry before
- a9826d451a971e69623fad7b84ff86b64606fc3a656c082307379210ebc258b5
- this leaf
- bec33b8f2f00df0109d38c5697a93f59e6bcd9a3a66668ab38c9f3b5c75dd210
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- yQRXBEkfVkfpznWcmFgXxghPogmhW+dmbIxK5438ivPyxF5eYYVZDhTrZDaNcS4pxSeK0NdkxfOForyCENfHBA==