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
- 8535d2c08baa1eb180c0f7ffd75ca9757a0a155a5aeea472e4bc8ff34b68b61f
- request
- be5a17679af8d3d8d242511b68ec908e5cb45ca98e9fa3a6b9336279a117ce08
- transaction
- 2a06167a52da1d3c5ac79fabf608309be7be0eb6f45e0adae46bf345be374e78computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22071
the chainentry 22071
- sealed to the entry before
- ec356d2ca9c2edcb9c6011800cec42b26992ed4f4039e314383b57f055ca9988
- this leaf
- da94de7af5cf693a150b6248eaa9397975129ed20af20d388f973b65e8abdd98
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 5diSJARVCSL9f2ZlpZovcRP1cArOl9aVxsg7817DKkGDiIWTvF0qU9Tg/DzleSeDoz1vYWDuw6Mvjinirnt5Aw==