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
- c3a1c63135e0253c1b97d27e0b6e8d9eb437f39957bd293569045eb1d7de51c1
- request
- d94abc571b1ef15119269320141ca9d5c1c03da5a89cf19e5898f4eaf48f1efc
- transaction
- 7b4008372c491817105804da2476df4a2d49fccc5db07a74df3773a81fadab1fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 72281
the chainentry 72281
- sealed to the entry before
- 427f9f67c3024043e9b4d3166f482207cb5d1da8c32bd0aa4ad971665a0f913f
- this leaf
- cfa6d5e9316a944806a9709c9aaabea9196a465a19b8fd84cdcf035dd3e6459c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- hN1o7AxRXj61XLowPJ0cz/2kBPsT6AnsB1QsjIgmQssFg22in83XK8eZJTK+Yb1WE8B1QcfUc30Lr0xHe3RJAA==