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
- 0a9e0675d91e7b937366f6fbe1472a9aea00d2d2b06644ef93f61d19acd52efa
- request
- 879b6fb4d27746a919b937509e6f04ed76ffd3a4fce3109e4620fd84ee32a857
- transaction
- 8618edc905092d414ad437bc99d9e0b1d7fd2283f83226c4e030f268526dff9ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 76059
the chainentry 76059
- sealed to the entry before
- f724a69ca0f7e55a4777f0e2b75ffb849f09377f120d0a4c2faecc6a0b803ea0
- this leaf
- 1fd8a5d26323900cfab1b3e37dc568b9e28078e7357ce324879ecd10320fac11
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- cDyMO4Gbh3Ld7CkwNHgbBIFW/UWEXHenhxj/daEKanLBqwGOvg1YsqOzoSIJFh4cJHLmKzzS6GTF3CC+DyrVDQ==