Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Current »

1. Description

Component for integration with MonoPay.

This component is present in flow types like:

  • Voice;
  • Chat;
  • Forms;
  • Service.

The block (Fig.1(1)) is used in space to build the Flow. The settings panel for this component opens (Fig.1(2)) when you click on the block.

Fig.1. Mono Pay component

1.1. Mono Pay block

The block consists of the following elements:

  1. The name of the component;
  2. in branch - receiving (connecting with the previous block) branch;
  3. out branch - outgoing (connecting with the following block) branch.

1.2. Mono Pay settings panel

It consists of the following elements:

  1. Token;
  2. Action;
  3. Break;
  4. Add limit.

1.2.1. Token

Required field.

This is where the token is entered. The token is taken on the Monobank side.

1.2.2. Action

Required field.

This field is used to select an action. The following options are available:

  1. сreate;
  2. cancel;
  3. remove;
  4. status;
  5. payment_info.

1.2.2.1. Create

Create a payment.

When you select create, the following fields are available:

  • Amount - the payment amount in minimum units (if its a dollar - cent). Required field;
  • CCY - currency code;
  • Payment Type - type of operation. For the hold value, the term is nine days. If, after nine days, the hold is not finalized, it is canceled. Required field;
  • Redirect URL - return address (GET) - the user will be redirected to this address after completing the payment (in case of success or error);
  •  Validity - the validity period payment is in seconds;
  • Set variable - a variable in which the response is written. Required field.

1.2.2.2. Cancel

Cancellation of payment.

When you select cancel, the following fields are available:

  • ExtRef - reference of the cancellation operation, determined by the seller;
  • Amount - the amount in minimum units (for a partial refund);
  • Set variable - a variable in which the response is written. Required field.

1.2.2.3. Remove

Invalidation of an account if no payment has been made for it yet.

When you select remove, the following fields are available:

1.2.2.4. Status

Checking the status of the payment.

When you select status, the following fields are available:

  • Set variable - a variable in which the response is written. Required field.

1.2.2.5. Payment_info

Information about successful payment, if it was made.

When you select payment_info, the following fields are available:

  • Set variable - a variable in which the response is written. Required field.

The structure of the responses passed to the variable is consistent with their documentation. More information can be found here.

1.2.3. Break

Responsible for the completion of the flow execution.

- initiates the end of the flow execution after the given component.

- the switch is in the off position.

1.2.4. Add limit

It is intended to determine the maximum number of passes through this component.

The failover branch appears in the edited component when the limit is set .

The failover branch will be used if more passes are passed through the component than entered in the Max field.

Clicking on the Add Limit button adds a Max field and a Delete limit button.

The number of possible passes is indicated in the Max field.

Clicking on the Delete limit button removes the limit and returns the Add limit button.

Fig. 2. Setting a limit

  • No labels