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
- d21611ff32be7458f32dc7d965abef33b266bb6cdebb83dbc1d44faf98fc1c65
- request
- 63368e755657889e0e27fe5bb4ffb96d91f4999883b8bdbcc91ceb36c21e2f28
- transaction
- 012df0c94ed56122bf8b91ec9b7097dcfd7c7a39e7b8204d0688546d4aa23316computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 35240
the chainentry 35240
- sealed to the entry before
- 365616bc6842543173e5479b0bff5b2d845080eb72d9559184fb18584eaba090
- this leaf
- 05544160ac941ecd123581a7648339d0b4445b9093547122ca4b4d6d684d74eb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- LkYNP3rAcEaVpOD4XKhPaEYmzJZK5bzzSyttgTgQ+cf3tlO+3893EdjRIex1iq1G0/n7xmBkMPBAd7FTn0fnAA==