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
- 6021ee487928e74dc1504dab85f56febaf6a6787879d09fc011c6ff50452333f
- request
- c020620c557bc170547ce35c430d7eb93854bc2ef6abc4870887a848be867c63
- transaction
- fe09353fc97476ce718eebe22395e2360540c586b2ba3a7c5b89f1eea3516140computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 38158
the chainentry 38158
- sealed to the entry before
- 48c0acff089f6643074b120c67fedce4e6e08cdd708559ba477665513e26098d
- this leaf
- 4d5bb88038fea27c1a8cf00945505cc81efb1dcf2ade5479198781df3586152d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Qu5kJ5F54xhZOFd2tGaGr6v9JBCOQAzr+EKBqisBhBrdxkZ4rhHSReFS4bP4hVMYAuyCiszniu5UMtf15yVmAA==