Vendor identity

Proving a vendor is who they claim before money goes to them.

Vendor identity in SigmaPointPi
/vendor-identity

Payment fraud almost always works by changing where money goes, not by inventing a transaction. A convincing email changes bank details and the payment leaves correctly to the wrong account.

Identity verification holds the legal entity, the tax identifier, the verified bank details and the record of how each was confirmed.

Where everything sits

Select a vendor to view its identity assessment…
Select a vendor to view its identity assessment…
Vendor
Vendor
Pick a vendor above to load its identity assessment.
Pick a vendor above to load its identity assessment.

How to work this page

Verify at onboarding, not at first payment

Verification under time pressure is verification that gets skipped.

Confirm bank details out of band

A phone number you already had. Never a number in the message requesting the change.

Record who confirmed it

Name, date and method. That record is what makes the control real.

Re-verify on any change

A change to bank details resets verification and holds payments until it is redone.

On a phone

Vendor identity on iPhone 15 Pro Max

Every figure from the desktop appears here, stacked rather than reduced. Tables scroll inside themselves so the page never moves sideways, and figures keep their separators and their alignment at every width.

Questions people actually ask

What if a vendor genuinely changes bank?

It happens and the process handles it. Two minutes of verification on a legitimate change is the price of stopping the illegitimate ones.

Does this check sanctions lists?

Screening runs where configured and any match holds the vendor for review rather than blocking silently.