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
- e2e81440be58492d4c45d09bf0db7ae0b83589001e1fb3f986990693630890bb
- request
- de4f2eb18f8adb9dfc33e230f4c367edb901f788827fe0cd22e49bd8a1a60b54
- transaction
- c138e17ee05c924614cdd8f485ce4da8d39e47bb24679b343f9f32769b4b8666computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 33795
the chainentry 33795
- sealed to the entry before
- f99274dad3cacec36339bf0fc0bf10a7668a1fa67e3a45ac874dc6041e507f33
- this leaf
- 7bda659eb6b183fd877a566931f4bda3eb21ced5b0ef40486940d0525658207d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- nveW50Vtdt0hXnD/coeBWgQymlx68csw/YcaiBjFRYnyTyc98IjStXVaPeZoyP5BCMqgDHJp4V9il12jlT2jBQ==