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
- 8e520a742e2ca48d45b11e4d8675d0fb28010e160844b3e33308607cdce4164c
- request
- d4a74b7ebe65644fffb4121056631075c20b831e95194c6c422f8c4fecd98c76
- transaction
- b8662ceb6c2f46d24920d987c6af6fa6bff5f3fad41f0f95c83b2b50fb4d10ddcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 111
the chainentry 111
- sealed to the entry before
- 9bb55cc7a2b26e3d8915a0e35b0616894c3a2d7a64ceb8f37363f3e3145ff9d2
- this leaf
- 2e4d5e12ed3aad164f41bcdc18752bf2ce3d21be5d39a7ec0fab780b4efd0bd4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- q8DAWTUTLdtWeLKaVhcDm/7vdW+23xg0aT3piMP5Y10dMZzTq8M32FF7dxEU9ejn5O6ZYMH80UqbqGom/jm2DQ==