Back

CRM, PSP, or Trading Platform: Who Controls Each Stage of a Transaction?

CRM, PSP, or Trading Platform: Who Controls Each Stage of a Transaction?

How many “yeses” does it take to deposit $500? 

From the trader’s side, preferably one. Click, pay, carry on. 

Behind the screen, the payment provider has a decision to report, the CRM has a record to update, and the trading account needs the correct balance. Somewhere between them “successful” starts getting vague. 

Successful payment? Successful account update? Successfully testing the client’s patience? 

Who was responsible, the CRM, PSP, or trading platform? To understand the forex transaction process, let’s follow a hypothetical $500 deposit into a brokerage, onto a trading account, and eventually back out. Each stop comes with one useful question: who can move this forward? 

Before the Deposit, Who Sets the Rules? 

The broker has a bigger role than our three-part title suggests. 

The CRM coordinates the workflow, the PSP processes the external payment, and the trading platform reflects the funds in the trading account, but the broker controls the rules connecting all three. 

In a CRM-led funding setup, the brokerage configures the client journey and internal payment rules. FXBO CRM, for example, allows brokers to configure payment availability, transaction limits, fees, conversion rates, and approval processes. The CRM applies that setup; it does not independently approve payments, set compliance rules, or decide whether funds should be credited. 

The journey below follows that setup. Other arrangements exist: MetaTrader 5 can offer deposits and withdrawals inside the platform when enabled by the broker. Even there, payment providers are involved and the brokerage manages the payment operations. The location of the button does not tell the whole story. 

1. The Client Starts the Request, the CRM Coordinates the Workflow 

Our trader chooses a payment method and enters $500 in the client area or payment interface. 

At this stage, the CRM records the transaction, connects the request to the client and the intended destination, then applies the broker’s configured workflow. The deposit may still need internal checks before account crediting can proceed. 

Think of this as the first “yes”: under the broker’s configured rules, the request can proceed through the brokerage’s process. 

Check here first: If the payment option is unavailable or the request is awaiting internal approval, review the broker’s settings and CRM workflow. 

2. The PSP Handles the Payment Attempt 

Now the payment service provider, or PSP, handles the external payment process. 

For a card deposit, the flow usually involves the PSP and acquiring bank, the card network, and the issuing bank. The PSP does not necessarily communicate directly with the issuing bank. The PSP can apply its own risk controls, and the issuing bank also has a say. Approval under the broker’s CRM workflow cannot promise a bank approval. 

There are stages within this stage, too. In some card-payment flows, authorization, capture, and settlement happen as separate stages. Other payment methods follow different timelines. In those card-payment flows, authorization approves the payment and reserves funds; capture moves it toward collection; settlement comes later. 

So, “the bank shows $500 missing” deserves a closer look. A pending card authorization may be a hold, rather than a completed transfer. 

Check here first: For a declined or incomplete payment, inspect the PSP’s exact status and response before deciding whether the provider, bank, or integration needs attention. 

3. The PSP Tells the CRM What Happened 

The payment reaches the status required by the integration. Excellent. Now someone needs to tell the CRM. 

Usually, the PSP sends an automated notification called a webhook. 

The receiving system must verify the update, match it to the correct request, and apply the relevant workflow. A notification that never arrives, cannot be verified, or carries an unmatched reference can leave the CRM waiting. 

This is where the forex transaction process can appear to stand still, even after the payment provider has reported success. 

Our deposit now has a second “yes”: the brokerage’s system has recognized the payment result, and any remaining internal checks still matter. 

Check here first: PSP success plus CRM pending points you toward notification delivery, transaction matching, status mapping, and internal approvals. 

4. The Account Credit Reaches the Trading Platform 

In many connected setups, the trading platform receives and records the account credit after the broker’s workflow approves the transaction. 

In a connected setup, the CRM can interact with the trading server through an API, the connection used to exchange instructions and data. FXBO’s MT5 integration supports managing trading accounts and transactions while bringing balances and trading history into the CRM. 

The trading account credit is a separate record to confirm. MetaTrader’s documentation describes an approved deposit being added as a balance operation. 

That is our third “yes”: the intended trading account has been credited. 

Check here first: If the CRM shows completion but the trading balance is unchanged, check the destination account, server response, balance operation, and synchronization. Establish whether the credit failed or a display has not caught up. 

5. The Trading Platform Handles Trading Activity 

The trader opens a position. Our $500 has entered a different part of the story. 

Orders and deals now belong to the trading system. Execution follows the broker’s setup and the relevant execution mode; MetaTrader 5 supports several, including Market and Exchange Execution. 

The platform also tracks equity, margin, and free margin. Those figures can change with open positions, so the original deposit amount does not describe everything available for trading. 

Check here first: For order rejection, execution, or margin questions, begin with the broker’s trading operations team and trading-server records. The PSP has already finished its part in this deposit. 

Withdrawals Need More Than One Approval 

Later, the trader requests a withdrawal. A few extra questions now enter the picture. 

The broker’s withdrawal workflow checks eligibility and approval requirements. Documentation or bonus conditions may need attention before the request proceeds, and manual approval may be required. 

These checks, the trading-account deduction, PSP processing, and payout confirmation must be coordinated through the broker’s configured workflow and integration. The precise sequence depends on the setup. 

The PSP processes the outgoing payment, but “approved internally” does not establish that the recipient has received it. 

Check here first: Establish whether the withdrawal is awaiting broker approval, account processing, external payout progress, or confirmation of receipt. Each answer points to a different next step. 

FXBO CRM Helps You Connect the Answers 

At any stage of the forex transaction process, the most useful question for your team is: what is the last confirmed step? 

Keep the CRM reference, PSP reference, trading-account record, amount, currency, and timestamps together. Then identify what should happen next. 

With FXBO CRM, we bring payment workflows and connected trading-account information into the brokerage’s wider operational view. 

Request a free FXBO CRM demo to explore how those connections can support your team. 

Share the article

Check out latest news in our channel