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
- 02635891e4db621b161320ab5d47ec93c9e0edec90253c592e0913547c6929df
- request
- ca309092f3ba404b8cec6cbb5d337eeb125c88433435dbeb08dfb0deb681e97d
- transaction
- f2d86e95780187f1b2dc1d0aceda3e9f67e4a55236e00c02bf1fea882de8c1b5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 43061
the chainentry 43061
- sealed to the entry before
- df953789c522b2c5696c36b4ef296ebdee7ac4512018b5c93a82b0b510065f04
- this leaf
- 1e75512fc0f2c458b4691a7276bfaca100a0f0fa69ed2373c55a17b380e9df9a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- haXbAvHmierbatKC9IForXfgREFtXZiWr2uLw3yFMm/ArkvCoJ3h4F+Z2W1Wrd8dGxaHshN9zXVaE31CRpsEAg==