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
- b5e5767819073836c6a6c48a49a8d85efca3011ef576329905d737e7efafb57c
- request
- 50cff27df73c6fde7dedd07a82d859d9b4b5e16007700598ad4557607c954edd
- transaction
- 8271f0a1bab12d59016ba87a15f39c36547ca47f6136b1a6ff7133c7ed60a3b3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 64909
the chainentry 64909
- sealed to the entry before
- 94c5c2704581ec2d4320fac6821ff2708a14d7f2807cb98a27c1d3e8ac974cad
- this leaf
- d4b2ace6571afc543b9753cd2b8e2060f02ed389fde2a8bb2a90ae6e3d692c88
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- UEUGHH19wNlvr98lhWLLQ+jZFDJ63Hze+e4h7F9Tt/tm4hyi4IZTqVyGXZIprhYbWpS5MhmezcfFiG5twmXoAg==