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
- 38087d0506228cc353d72383c5deac187a103bc39eaf68d226ebe99525dfe7af
- request
- 6f804904dc6919cd385fff8f133f3fa91bb37cdf5d6c5f374a5c72c1c7bd85fc
- transaction
- 7b8949b95f1edcb539837b637319ff93bc4476a14a2dae682f55fbdb8e83f1b1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 281
the chainentry 281
- sealed to the entry before
- 1cc66c12b46672ec067f5b2a64ba5a7dc9d97dd07b9fd96e0339081a04ce5e2c
- this leaf
- 59377f6127f121c3c3dc56e31c8ae4d173c7ddf5218d303bb32d3779fe288fd9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- RcR6hcTYUpMqlD3oU92RldvK5eUsyZMR6KFrUgnXpAiJ+7drHiqhF0KQRoUrjLtK2G7LVCxA7bIJApP0MLGfDQ==