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
- 0a0731c0b39f67455f6ae67ed2a7a801a30e7b87a29f1e481e86d9a006c4a0fa
- request
- 113e9d70779a41ad84dbdbb78bb2212d06a187cfc76fd142ee75c4a7bdb48fbd
- transaction
- 6a180e0535f01468915659b09819b22899dd776c3f5a2999b525dfab35c6d511computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 51240
the chainentry 51240
- sealed to the entry before
- a0927c8cd6d476431fa7268144f5f29f74554ef987a0b028ce3fd43978e642b9
- this leaf
- 37dba093ac7ba266f9a2dc0fafc19fa143fda858233a403f6758eb0322b5cd28
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- EoRlIHlxSHcUx3ezCOsRkVSKSHxdEIqUik4SQhHD688c7oWi/Y2M5cp8ZDjel25/1XMpPq0yjq+He7aUnQUaBA==