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
- bae4b1d70be366dd9993f3fdf7dc3d823d41861449a43319cc03b87468fad594
- request
- 54f75a7b21c97eb6cefc56fcbd57570704f18dfb426dbbd1060fe735003b017c
- transaction
- f6939e270ef21193841f49d18acbd1d2f3bce4971e7c88a620c7a1a1e0d8ec63computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 18830
the chainentry 18830
- sealed to the entry before
- f5362790c3ea0754219b28d0de120eaee01dc2b7b01f3f0dea51cad0bccd1564
- this leaf
- d1c461449152a740f3e0f162a2af7eb875a14d42e3c3b5425695cd2df9fcec0a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Yx6xjShgh4BrBW0fJUdCQcUjbdGLBEIe90fN6ZCFKtrfOkTJKdZ1d2hoeDdDZh+eUTidJLqTzpZmON90bVTSBA==