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
- ece4afbfd5360dfe6304f99a1eb9a507fe62d4791c6437173c49085410cb7d1c
- request
- ecab5e65d8b31690cdb661543588af0ba70752f483d23cc15f150fb474db45a5
- transaction
- 59b3de9e629aa4658efdd78777c2f80c0f007443ed8e102efcb81f3396ee5382computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22363
the chainentry 22363
- sealed to the entry before
- 75dda71a5c7ee374aa2792a3675653dace040db5265745b1102c27fdf32f9b6d
- this leaf
- ed3f4c78e0e58522790342ab5dd9333c905771520035c1d0def774d980e47434
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ut4bYJQFQTC98dGH9eGqF1S7Db8o2vyIIdOzzEiZmVuMXpwNU5DtlNd2Cv7pZXb9bXwKQWpvkHKi4Rsq1HytAg==