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
- aeee419d10b3c0fe011f0258c209c210a171f52bf8d1a40b239eae234c5c87a6
- request
- 099b3649c7e98428df191cc756a86ddeb91cc6c7076aa07bf2fe20b566e90d95
- transaction
- a222833e3363debcfcbec852105e6aeb18c071c0e8805bc1bc8db3f4537bcadbcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 21585
the chainentry 21585
- sealed to the entry before
- c57fc49cac4acb260bbec2a5668a49038e5ae31e5a3e10653eeee7210478bc63
- this leaf
- 6d274c9516cb77131cc1d3a10e037a4da027f267fbcb73d04609f8a731b3eeb6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- gUSKT14O3QD6GLjDZc1ufSdCy8hGyL1NrjtZA/5++Es7kVnd82ccPRd0Sp5wX5vUwy5sSLZBo9Xz0kJbDlvZBw==