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
- a01b304fdb0bcec9c26cfd75c30a738af01bd1a19ac3d20a47d08f16dad14ed5
- request
- e63afdd2415f8223c2f5f368d573a574bc3ec74e64544394683a19840980b2af
- transaction
- a77f2f6b5d388d31c4ffdd6730354dd31ce2194b31c5ba41b9df53c6d06909a0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 60584
the chainentry 60584
- sealed to the entry before
- 9d533fdbb38ff0c4c3948bd4f20e46d38a45dac5287950314cc4bac34b321969
- this leaf
- dec55602dfa2187e551a58f0c98aa307b4e4b8b9b9e4d56c942e5653313adec9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 9D7iqamf3L1TwWliW0BWtbp2xP/WBbKx7xu3f/JyvHQ6jcc7wIjk3ATKcJHWH3g44PNCmSXT31Gkq04/cIl9DQ==