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
- af566e3a96126cf44769e6995da74ebe05d1539322c1e4afc4256f852919a918
- request
- 1dbcaa143c4ab580296c2da20002d22fbceccf5a75dcf5086bd45ab321b0ed13
- transaction
- fe1ca16b86b2e4cc442c32489c759bf98c8fc55f594ff3d05432ee644bc0addacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 5497
the chainentry 5497
- sealed to the entry before
- a58cdcd607c4ff0fb5da8c1ea54ced767614c589cd29900c86ffd6966a61eadd
- this leaf
- 49f2910be2a53a86241d9e498d1881df5f30538e12f97ee16d5acf7c3c10a8ea
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- PyjyNNaLFQYF2GpAOJlVNjZkc1wvoSCHXg80sOZM2dN01z/2ltI9veU1kLnRitOSQVfaE36vgXxgShKb4ttUCw==