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
- 6f9cb0cf4ec3b22834b8ce27182a4d34f0719a04cae6c7eeedd4e182677e6575
- request
- ddd0e16715f907ee4c7d0aedede80c472f9766d81f1ac70ffa9a5f0dab34abd9
- transaction
- 95782a85d5fa0d8f85d0dfad2cd6cbec29a95ab0af68b46a397cb2151768db4fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 48664
the chainentry 48664
- sealed to the entry before
- 76274adefcad364836a4eddb723b863746bc5ef02ba5cd6f378a1c4bd514b604
- this leaf
- 9be32636001d1a5f2c094c616a18572013479a36679e319f7785d8f7d8874415
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Ac13yzNo+JM0oLGpK4R26JAeus21OsKbbltmm+I30FYNo/Y5hh1vGMD3GhNpXPC70G9L96sgkjiG1l0Iar7hBg==