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
- ebcc961f3de1d3421803e9a9c9539ff46dd44c3babd77c0644e2675b9a7c924d
- request
- edad609c8411ef0df32ea1a36d61afb4dae7e27510b2eb006b8dd5c64108f795
- transaction
- 5bdf2b9bce640d80a38100015d30d122b0980122533db791d6e56f0b5761d0ebcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 19200
the chainentry 19200
- sealed to the entry before
- bc60cb6c9a0da273a832cee0b3016085c0a042cc3ec37cef5040ce79f11c4f0e
- this leaf
- c8fd4ce8589ea2f0b5a7018e344268d551a55d3f2ac2d8fbfd46deda2a64b4ed
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- OwpU5gsfWujjTklwuJhKNLmBeXvzeK/V7iSzi09bqYm2iJDraaO/vpRxIpuVxrM4VVuwnbPzmBpfZs30/zyNBA==