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
- bff95ed596273cdfb04cd09064438ab22638139fc65882b244528fb4ffb69536
- request
- cb0b54df0b2a77bac3ca3d1fa16971bfbebf680b2d7746eeb7aab9d82f1d81f6
- transaction
- 08c02b4e74722b2476ba5f91de0a39655e2931ccc47702db3bd23dbbdace0a1bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 35114
the chainentry 35114
- sealed to the entry before
- bce28adc59bc81b9bee14af345f731083c985de06350724dd78da518222fd671
- this leaf
- c7d866f34c219268171be3dc7e47f0cedfe17599bbfcd05fb405862e21fa8440
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ++cNZTHb5CsxGCHWfsfRTVLA/Cp5MUHDWb7JMj5VH83kpCBt5sIN7rAapuvaHPv7UR0xeHf/SQwZBzalLWxdCQ==