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
- f28e5bd1161ffcbbe93edd41834aff4932cbf32a9347ca9dcf858aba6ff2300c
- request
- a7f1eab1f16f91d5b36a2f535d377d1cfdab7efbad4cf8f43f80f4c5d189f0b0
- transaction
- 959e23942275d6371ce8d0d4f027a662f0165099fe70b14774d8f88e82071bf1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 7474
the chainentry 7474
- sealed to the entry before
- eae07ac42ed6c3c7a9adca123fc3ebfb67c689e2167001351ebfb05389ce2c58
- this leaf
- c672767c52f914573aeb52aa790df3875ed0ae1f8d64876b0d14562787014052
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- V4qgrU4d3OPfx9Mw0Kzb687pBmrhjqlezJV1OqZAS6mb06EVOglH6+WoNSgBkmtp49xjsXrcsjcJX3xxMTfyBA==