CatSimba · professional workflow
Why payment orchestration matters
11 configured gateways and four vault choices support different merchant setups. Availability depends on the enabled provider and supported gateway-vault combination.
Why gateway choice helps
- Respect the merchant’s existing processor where supported instead of forcing an unnecessary move.
- Choose methods suited to the transaction, such as ACH or cards, subject to merchant approval and provider terms.
- Keep options available when a provider is unavailable; this does not guarantee automatic failover or bypass a processor’s review.
- Compare provider fees and fit rather than assume every merchant gets the same economics.
Why tokenization matters
- A secure provider entry flow can store the sensitive payment method at the vault and return a reference token.
- Store references rather than raw payment credentials in the intended CatSimba workflow.
- Use saved methods only with valid permission and a supported gateway-vault pairing; tokens are not universally portable.
- Tokenization can reduce exposure and PCI scope, but does not remove the firm’s or platform’s compliance responsibilities.
What happens to the money?
The selected gateway processes and settles funds to the professional’s or client’s merchant account. CatSimba’s intended role is orchestration, rather than custody or pooling of funds. Gateway, vault and transaction-provider charges remain separate.
Provider certification, exact raw-data handling and compatible combinations must be verified for the deployed integration before live security claims are published.