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
- 173f8f5c6ac46239d4a20f35ad2249151ebc3f65766171530df9631784992278
- request
- 71d0e43d6600c3d691e237cf74604ee88a3090f84d15eafb90832ed23d002ee7
- transaction
- efd424e5b8e1ec4be1469689ef3296161231b1e221a0ef68ce0be10df863e4a7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 14381
the chainentry 14381
- sealed to the entry before
- 1acc93793a45aa6c57fb599e6c3f7cb04b26a98e502dcd603ce753c2a73435c4
- this leaf
- b5ea9612ea91c5b4cbd4575bea1f63305a2ad7baa9cf65abbac7ea5cd0912ea5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +mFR3ChrNprxOcIJhQoEmY/Mvy5K5aBnJ2hyvnKxxO7d9ep94yz1jaws2//WzY4OEJpj05smfNzFDdphyZrpBw==