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
- ccfc11707b31fa6e829513567dea0c584135e5f3d491fd8adbcad200e0d5b23b
- request
- df0d8b3043cbfeb2324f0e07c41da3f1793bc09325a2e8b23684b81eec212a8e
- transaction
- 975d2aa5f56e58a4dadf9c47c8e48af2b30bc44ac6cd9fc52a849470267489d6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 73820
the chainentry 73820
- sealed to the entry before
- 0f9f1e263776a3f1bd091eca5cceacbaa696fa11e678961feb96ddebd9a39a0c
- this leaf
- 28ebe2bf1d30751624c37f72881712d04abd58d7344e2b05d9fe4dc0e34a3d9d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- xKnN2DpHOWyDVE+vm3/zPrRftWtKBNMkRz/GwKzAuSVqCg13UiNC6h8oJVjYJn8DqceA5vFGEaWUyWrvpJpYDw==