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
- e570bff821ad3f74e4129c49d9ef58eb5e4be0153832f8c54302dcfc135b4d17
- request
- 2ff97d9c701ce09d562edade8dd256ac12ef524eba534461ba3163a2b2a7d077
- transaction
- 3b071bc7323f8d1ec43a708dd2a44ddc5110efdeb37462c0b0bd3db46b7f2cc2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 266
the chainentry 266
- sealed to the entry before
- bc2e9d255733bc5dd9491f84dc220dea5d703c8e76f899803d4b0b31316dc33e
- this leaf
- 1713bab87992f5dfb4db84bd43dd08f11197c76672c9aab26e538072e906ef37
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- VdyOY+WY+b2C8FdlHqHjv+807L8e8gLYznmcdArIsEzKEl4HxW2bc6AGw3Rb8TP67CED2NpbtBGIWq3NIJCmAw==