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
- 5bd35b7d319ad5610847126a6a7e238c1bb7a2f112086d57a40d9f811914406f
- request
- 555a248a9244df457e36c8fde288aca3f3c94740793dceb383a1f3f71eca9c77
- transaction
- 06fa470ae6c94e5f54bc472ae0117bfb357698dfdea7c3875c32785622d8f46ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 3004
the chainentry 3004
- sealed to the entry before
- 3c81dafc2366d33a67204ec54883e4befe348d467e9beb506851012f7dcaa529
- this leaf
- 0392ce57ccb0b8c1402ba6d4a7b0d2767638eec4d1f3edfdd8805f0c52add2c6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 329DCzbYGJ+4WdLCBKKZ3GC7sopkeTFMeRXV/D3+vNvXGPnnUSgTfGHZX2ykP6VJjU7Gcz3s7nBMbEn9Y+IoCw==