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
- 2a9c0a7e350cd73f34075185865a4065a1f62958dfc66d2c9e1d892c3b9418f1
- request
- 9dd951244af37d4e7a80ca4870047a83d69c86a78835e27cbdb47e36f97a7b25
- transaction
- 0d21a18d0a4a128dec6b85b6dbfbff7ca8588ca69bad393e7c5970dee6e8c64acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 67597
the chainentry 67597
- sealed to the entry before
- d71999b222b4dba9cd25a6f67b95d528e6f34b884e38ff9fb8e34ac744706e2e
- this leaf
- 3d4a7a34c196e75d8e266a26ff977bb23b867362437e1d543b9d5559e9924c25
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- unlrgYEwwN7TdlvjHkdNdVQGIDqkvUhJS9gStpIC/NJCNWNGlkQhuYxvpE2r6Hu9fjm/RdlTI0+A15IftHn1Cg==