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
- 0e44e3f5b5b537afd9c31c2612960abfb71b07f0ce859b383c557be17568fb3d
- request
- 5ad4630f171d3553dfce04072da67e7c6865a843b62ef37555d299b43b444a7c
- transaction
- 37830e6337a7d2ecc1d326ef5d002fcde72e666b3b3b52545289519938e6e3c5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30477
the chainentry 30477
- sealed to the entry before
- f8f7c0cd2ddb9772158f431967e322a5a838cae65aa91e14e882e2d900a06389
- this leaf
- 12179f311afc76a6e6b17a75d8bd7be708febdbc24215375e06d41016b70a191
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- lLLdfd3iq6zp6ylLijLqXRzGAMzl5ig54Cr3ZX1m4Et8wu/0Au6WEu12XvYrZN+gekF3FG/yOifWaq5b+v16Dw==