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
- d29b075715268500be8456a4db95c71003929c89f04dc32d5bcf011e81cdbfd7
- request
- 8a8f9950f0cf3f87cac0f0c583004c6a0b6e4a9918a725279de6a6df03039eb5
- transaction
- edaec44e2c585a541d95e2536c19d5dfcec3f7481296f9a638c687d038bc27c0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 43531
the chainentry 43531
- sealed to the entry before
- 41386170546c4a0423f367bd1821c5c6a6c8f488415e1a470313bf7d51707de4
- this leaf
- 43874bfeb0b85f15acfae5f7ce54a4de55d0d898bd3f7c01ba3734353b2f2905
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- OAq+lNWSxCBBZSpC2WjdwIQOPRCfKyQzw1Ak2yKljWohkGxgNm8C1iES9Jyfk9eWY9eJQjXvFYGOQvVEY302BA==