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
- 7f0617fc3ae3b255466c290ee1b556aae0dbc2ef8097682f873971da0ceac09a
- request
- 08f267b8e1180307bfa7e7bf0b4add05d3425be347a99166741dc52a7f46a861
- transaction
- dddfef407acd45a1382973c0721c4f68b143396d3891d578559c830f135c0e5ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 37452
the chainentry 37452
- sealed to the entry before
- 44f0a4afb1eb8a915eeb9a887ced964ea94c2854c3553a4ee51b3eca3fe2cf23
- this leaf
- 5ff09446e12b9bd0d5604a942c750213aab70623bcc03f7db8e7763cf724a706
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- JVEL1EErtqG97P5eXh5THQAkdsVHmQiqRyE4C6yrtUSY1nmkmrTKconKET9ceMR5xpQdllNQu7Zn2mY8DVULDg==