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
- 061a60598634434b17470ebede20cabcc6f26a46c5691658908fda3657887274
- request
- 45cb2b2cb3263e2ab1a88ba32eaa2f1e6d3a7d194456b6b5955b925baea74356
- transaction
- bc39a9dcc0b1290d356042c504c3dffc40217367a8ad164fc416b585f9451d66computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 52629
the chainentry 52629
- sealed to the entry before
- 4dcb3327682cc3818fe4d3bea8f0ef9f41490fc799702dbfaec5b6814ea95028
- this leaf
- ace49285d334e85dc417f5356072f5828f7ec2072c92ed0ce52be08268c7175d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- MQOvLgolgPIWzp6eKoeQSYjgTkY4SjUlCCTaXgwhSTC6pZk86SSi6wKYuJDqHdb/l/MFgjCYrWy1kSMYy7jyDQ==