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
- 566ecd837aacaec7e51444af4b1b1a8bcbf8b57feb07dcf4bc8fcdae8b34a273
- request
- 6a756fe4b91d17d293cd1d9dc9e78a9f3773ad498aa1115dc06b12573eccd490
- transaction
- 4a506041a9e68a98f02745f6b30c6d879fae32eb50f1446b79993bcab668821bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 72131
the chainentry 72131
- sealed to the entry before
- d419db99d3f17fc9e327b9772984c87703617b35612d9c68eb4ba5584f57227e
- this leaf
- 77cee34158cacda6543e301077790fddc1ade8985a5c848a9ed2948b6082aff6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- A7wypf6ngo4OPxsDHh0sqZ+AeHHykVUM5dy3OkG5noB5faaPm/DwoNOrW/lr2CivQI1bp6zXvwLI421ckVnACA==