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
- 3b2c4d0d8e34fd338f313c0c4f0bd1c5bab7fd1c03a323d923584df9a6cd7409
- request
- b4a783f7680ae23454bf0b4c0b7d965f836abc7ef4fa43a7ffcd91a81c823de2
- transaction
- 4b8c0ba37a50bc990bbfbb169d9e895b48202f9a66f5ff2be41ff1b0996ae61fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22841
the chainentry 22841
- sealed to the entry before
- 19ae2cab367d03bdd4b7193156bb22d8d93de6268e237b62ad020f7337fb4a48
- this leaf
- 90983d8b8ca73d239e44c04c226655d4c720c0359561136155be154b241d7ed0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- QDvcKGWsoFK6SN/6VACHbrCxJlAiPV1eiSdyOCUUiUWfMpSHUJ+GL8VVvGup6aoqXGygZIOBecOqcnuQaXG3Cw==