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
- 963d2a55f6359ec80f97ad9fdcd813c23e6d9b5e5d5d8cf6c71a9ccb7b5fe51a
- request
- c79287bf6f4f685e02296013a8c14c5dec92f38560ce7222b579cac0d5381066
- transaction
- f13df4ce5d50f3affd20b68128234bef8a99bd1c3dca5db10540f5b7b84f951acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36249
the chainentry 36249
- sealed to the entry before
- 6683f6ea49145924abf10f4294b3b9b6ee61f6dfec119a6429c3f3e03c14b2cc
- this leaf
- c11f963283c4a1aa817cf8e744a37002fff3c24b94a0824aa6e5dc051a327744
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 7qgJ+tNi7OVQNie+MRu0u0yL8nKR8EiPXrMl54VAaFUbw0Ya4q766p3PkY//r4AvXWoW95/Pg9s4aCLRBEp4Ag==