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
- f6873365c0d3ab9982d1ca51d445ab37faf5791abbf4bafb6d87f3c3ef717a09
- request
- 02502deff77cca083ce1be7662d73bc88001d2344c5b994d30678ab3514c01a6
- transaction
- 838fc07f5ef0280695b407be54d5c22cb1994cb46ea2499b1a3ebb56054ddc3fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 31588
the chainentry 31588
- sealed to the entry before
- cc73515bebbed8f183caec9a7061fff5f323cc4cb6a2fa3af5928a03af0c6e50
- this leaf
- 36b13c99d43a1e4e00b2bac22a486c660f5c856d7dae5bd38550df88a6c28550
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- CIQ47W7mcfFjf9s1OQdo522Hq648eG0Mutz/9eHvPtMlgifRo77oSPU5EbK30WzKJSRbKXahYlZy138IwwmWAQ==