Skip to main content

Suggested Operator Implementations

Discussed below are the parts of VIP Connect where operators can determine how to handle various transaction flows that best suit their system. This is a listing of those areas with examples of how an operator could approach them depending on system and business needs.

Deposit Redirect​

At the end of a successful deposit request, the VIP Connect API will call an operator’s notification callback endpoint to notify the operator of the successful deposit transaction. A successful acknowledgement that the operator received the notification message occurs when the VIP Connect API receives an HTTP 200 from the operator endpoint.

  • Default Behavior: On the deposit successful screen a patron can navigate on the web component or return to the location on the operator’s site from where they were launched into the VIP Connect web component.
  • Optional Behavior: When a patron returns to the operator site from the VIP Connect web component, an operator could redirect them to any area on their site.

Withdraw Redirect​

After a patron’s withdrawal, operators are directly notified via the operator's notification callback URL. No other action is taken by the VIP Connect API until an operator approves the withdrawal request. The VIP Connect API sends the request data and expects a response code 200 OK as successful acknowledgement.

  • Default Behavior: Similar to the deposit scenario, on the withdrawal successful screen a patron can navigate on the web component or return to the location on the operator’s site from where they were launched into the VIP Connect web component.
  • Optional Behavior: When a patron returns to the operator site from the VIP Connect web component, operators could redirect them to any area on their site.

Freeze Funds of Pending Withdrawal​

An API call will be sent to an operator’s notification call back URL alerting them of pending withdrawals. After receiving the notification of a withdrawal, it is the operator’s choice to add additional logic in their systems on how manage the pending withdrawal.

  • Default Behavior: VIP Connect sends a transaction notification of a withdrawal to an operator
  • Optional Behavior 1 : Operators could take action to freeze transaction amount funds in the patron’s account upon receiving a withdrawal notification.
  • Optional Behavior 2: Operators could set up automated approval rules based on data received in the withdrawal notification from VIP Connect and approve the withdrawal based on business rules and requirements.