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
- 878a14dca5b6fb70829aa448d2530333efe2fc00083ed36becffa735914c00a7
- request
- e879d053885bf3fef15a7434ac2c8080b5b671568442b47442903feea8150bff
- transaction
- d6b53d3ce240282e7d1ce9c5f06dfb47e2d89ab1ad39a9493dec82ae7af874ffcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 43466
the chainentry 43466
- sealed to the entry before
- 274d0cf094ba7279c8e15789393c2abd424c5eb56adf64312141d72da8659469
- this leaf
- f257e26506819d5189bb9efde838a8607307a863630543290960d8991eb768c0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- UP5G4vDMa8M0Gj0JDpvQdRYTaQQQAbAVuSaT8PTyCVt6t+wHqJk85TLU1Eladiqiu0JbLt9M5xoVJ5zmcDXPAQ==