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
- df1773d63ce1650ed6ac1a3b66ff079ce92808d6c316b286edb6ad178b7cfc65
- request
- 076c992191025f10dba9ca95bc39469bd6e97e8d523052ef9e4e0f944cbc4dcf
- transaction
- 791e1835f75afba18878014496303df4101b5398882ddf44e72b2bb2edd2efbfcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 19122
the chainentry 19122
- sealed to the entry before
- ffe93ee3d7df2f3955f7e5038ea6da323ccfdcfbe0c80c7fd6a927881fb8a69c
- this leaf
- 0b2ae950762cbe3ca8900a5c73abcfaf6f6fe4e7efc0e822a1c11b4b918144f5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- leXe9PHQSV69OcFSziAng9mKQF4oxxQ8K0tr8JqyApl/nxyMQsZLwYn3CC+RW/992d+LE5tPGPwyH5wBM93ZAg==