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
- ff83fb12ca43e6fc5ab28cb16b664af42f0c4f63e2522417c95cacdd1dcf3e17
- request
- efcc850cd84b73e8d1315dd038956575278e494eacc4d204caff481d3c8dc1fc
- transaction
- 797ec9530029acd35843ea8a78a2c6e3e9534290a7f0c3a2e0dcdbfb7e6e6f94computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 41465
the chainentry 41465
- sealed to the entry before
- 4d7351162a6033ede1c61a58e065945a80a02a6cb855fdbec7f9c1eb137b7aee
- this leaf
- 09735130cd479adaee62ce0fdbe4eaeb28babffb85935863dadf01ea3f14fe18
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- an29kfJPpBdnrbhU3TmAiuQGSFTldv4cyjvPG0R2FKlJm7LyElCoYPsMNtJXl6mgRp3k8U1wadmmjYSCGuyuBg==