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
- 85b15f0eda3f69553238aa9c2cf99f2bd78959ef3cd84f671877e98d4169a94b
- request
- f06f83fb2172272a12aac2ad59dfcb4fd699ffec11eefd7aff5bd1fe28039514
- transaction
- a7ef3b7608c80afac3aef933331e2bb26491107036568a76cd97de74875cea5ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 48904
the chainentry 48904
- sealed to the entry before
- 08bc1ace31c080b292bd9ca150e87f4acc31a161d3c05a7125f07fe82be02521
- this leaf
- 63da39a892d985ed9451c9f4a416b67a867f8d52ab93a64801279d09dff23446
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- QpP5TsJgGSbOwdT5PX85pzKx5QddmEsj0yIbW3GzVgo/a1eDR7w/XCxHG4UZLifK0J+KsR6LyKiMUq9K9GepCw==