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
- 3c0fa80f9683d4db7e89bdf7aeac87ebd8a7152b4d61565ea1c0bf361b0a6b15
- request
- 52a2d2a47040e53ee933779756852186d47c40a8e4bbd044ac87b8f8f2f95384
- transaction
- 18434a0bc19ead9ef19fc06f0364bde941b4de8e03c904b6b828636cde6c8061computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 34973
the chainentry 34973
- sealed to the entry before
- 0d8ab2aa6816d73de778f2d27e5c33663c5cbc8f244322e7b086d545aacfc646
- this leaf
- 517abc3b6fea2dbf50bdc1f66ced16aa10bca94faf1cc5cbab27d545629814db
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- XbnyBiDAsoXEjoJBk+h3sk5kk54yAkUf3Lsx2+V2p09fV5J1vEsVcxuafHna3lmb7lNEeZxPMqmnqwua2rnKCw==