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
- c41a6f4dcc0a9a1d1625ec12d4496b99d2f44ef8888a34826b4daa5cbe1317e5
- request
- 35c2619a6ea8f3932f4edf11864fca716800b9327ffe21c1adf9550aa477213e
- transaction
- dfeba04092812efe94a53ad59e88f94247c153148682b5ae88b6b60296310977computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 15392
the chainentry 15392
- sealed to the entry before
- 7726811b888890b6e86f34f2e578dd42b7207a39416543b37a8570c2da433a09
- this leaf
- 720b2cded5f87326f10c8f40d118a781d443db308dac258f4ce8cb0e7f0e0754
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- lCCqxJfTUpGckN310aM+S8SVdhVI2Wt9UNcEMueUorrbU+n85ccUJTrlkVkVbw0R1yr7DiV+MCB1sr2LddvRBQ==