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
- 59d75d8a1a5cb747b611650fcf70a1c919c377c3b47301f585aa3ced973f56ca
- request
- 662cadc79c8b9e11e77316a755065f5a7c98f9f1346ebfcc9b16c674c4ba5d67
- transaction
- 934f4ffc14b69c351408bc49fcaded253a140b2139613cf33f977a9b424dc58ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 38471
the chainentry 38471
- sealed to the entry before
- 2ea453b810ede5afb14c2e555b70efb7d86a92f1e8f0f8d46cf3babbcef5a2af
- this leaf
- 070c5b66c33df490085af3bfd6c789506a3b433744f863eee9fb3e64637c80c9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- fXMRFTECv3DGVOzEG7ndKGmyC3j8rXKllM45eK1txA4HUvTiH2u7m5aOj8ccvkG2dJRdoCPbxFTpYQjI10o1BQ==