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
- 430c3eef30f47a500eb6768f1bfd77fe4b52a4788508e391ddecbf59219b9084
- request
- 575b987ecf148365ff31da7eda93b59464203c398c9412ac433104491f899967
- transaction
- e5d5854eb3e6f65f2e2c857501659bc9d71a1b9ac89e6cf4abe97b492708fde0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 32880
the chainentry 32880
- sealed to the entry before
- 6abd42c842702a311a08acaefb46aacdfd976efd6c1aeda5e430527142b13441
- this leaf
- c278f65447e610d60de469b3402707a689f03523d22a061004f2225eb1626fe8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Awujwy4HVNCZqBJ6iq4teEL1ct4HQ1Nwwkt0+1eOoaI/O+cwXkR01S2b59/0GHozWWhKReKsehuS/mHI+jUoDA==