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
- 03c764a1305e51fb7c3ebc116593bde86334d5150779d12a67993620b1eed659
- request
- affcc28b233158584f1d47569d3daeb01de22f63f97c0637deb3b92044a51359
- transaction
- a7a8296942e1475315fbe1e52b652d1ea4e02013b118ad07c257b9f6a7b6cecfcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 3640
the chainentry 3640
- sealed to the entry before
- 8c1e5d02a26d572b4774670b6693a608eca541a4e3457f5b205f12a1b3170ec3
- this leaf
- 2ceacfbb2c8f067803fe2289abf3eb9ed524c5cc69a99fb836bd352ea074573f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- VbZbN84tMrIDiCP0O0fcG+IBg9smpFdePc224B+gaZM5k1TuM1yRGv+WVKtDJCbIcXXdfks1yjOCkfpuJw9UAw==