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
- d943fcf4099b43e69f1567945487f45beee5daa74f7c0d3a26be581b2520d230
- request
- b1ea8d84a2f0fae725a357720121e1342cf8c3b3feea51c90535ef7a440e0eac
- transaction
- 2eb284b7aae2e263eab6ead971921bb205af319d948ed9d4b432061e54661917computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 54004
the chainentry 54004
- sealed to the entry before
- 487f398f93568ff0cd9944888fceac324f43b7966fe083e9d6c29733304f39c4
- this leaf
- c4d5145b5c1410fa4c6190d734391fa6650022fdb301998f45f971b2dea80cd8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2/bVJKZTsiLSKLL35VmEx/weI0shZwhik6iMsDDXv4rxdpAjKPAxR/m7KcT07Fhy0XMwS19QSjqeO0Tn5pHFAw==