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
- 066e9e9aca69eb970aa4f0663cf397b21f1d7eb321ca638a0f6d0a60e8a6d755
- request
- 1717856e503c20726000635870d85d67bf6707703bae9755d12df80a824a72f8
- transaction
- 90bd3c8feefa200862fbd173bdd00b1d298dc0190fc220fba34c83821b8c465bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 19180
the chainentry 19180
- sealed to the entry before
- e82ab9b5f03752b9a2c8241d55d154d88d061e909974bc6ad0f6e9794b9f9a00
- this leaf
- 9d399f85eb441447d054869f795e0cfa9f271f9fa4cb61f26d8067264ddf740e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- kaFACjnviOpcmpRDN3HbfUy2HlFNP1JfqqhrA53wO48UgZSytNXx4FOTJaZdoc+oFjRxyuUOntiuVpl1WDafDA==