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
- 79104169681773311e2920eeca280f8410343d75b97fb1fb5271eb3e73734fae
- request
- 6fd004d91e2793aae007af9594f680bd8e7ebb26a476a2deca4626a6990946dd
- transaction
- 13afc45d1b896371add21bca66dcf2feb80df95dceb6bbd25f18a9e59bb53edecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1405
the chainentry 1405
- sealed to the entry before
- 098f5ee12e49640e07100d053294751dca373df1bd60386a37bcb0dd53385a64
- this leaf
- aeebfb2cba720e4763742ada849f11865f2fa3232bb7f6a685966c88c4402a3c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- qnI4caE6xPsQfhuTM5mBDwyveyNBlkIMylQGNT9ZTzGqv1l6jiVWATOkA9Qv1R7R5R2WDE4baZafpKXTiMNsCw==