Payment Flows

Execution of H2H Payment Transaction (2D Secure Flow)

  1. Solid responds Merchant that the request is received. Solid decides whether the transaction shall be executed via the 2D or 3D flow. Solid sends the request to the Acquiring Bank to determine whether the transaction may be executed by the respective payment card.
  2. Solid receives Pay response from the Acquiring Bank defining whether the transaction is declined or approved*.
  3. Solid processes the Pay response and sends Callback request with Transaction status to the Merchant.
  4. Merchant conducts the necessary actions on its side and responds to Solid that the transaction status is received.


*The approve status means that the transaction is already executed.

/media/32/download/intro%20flow.jpg?v=1&inline=0

Execution of H2H Payment Transaction (3D Secure Flow)

  1. Merchant collects payment card details and sends Integration request to Solid.
  2. Solid responds Merchant that the request is received. Solid decides whether the transaction shall be executed via the 2D or 3D flow (Scheme 2 refers to the 3D Secure payment, for the 2D Secure flow, please refer to Scheme 1). Solid sends the request to the Acquiring Bank stating that the transaction shall be executed according to the 3DS flow.
  3. Acquiring Bank responds with the ACS URL if it is possible to execute the Transaction.
  4. Solid sends Verify URL with ACS URL* inserted.
  5. When a customer opens the URL, Solid receives Verify Request.
  6. After customer’s interaction with 3D Secure Page, Merchant returns Solid the 3DS request.
  7. Solid requests the status of the 3D Secure check from the Acquiring Bank
  8. Acquiring Bank returns Solid the Verify Response.
  9. Solid processes the Verify Response and sends Callback request with Transaction status to the Merchant.
  10. Merchant conducts the necessary actions on its side and responds to Solid that the transaction status is received.

     *The URL of the Access Control Server of the card-issuing bank that is returned in the reply to the request to check enrollment. This is where you must send the Payer Authentication Request message so that the customer can be authenticated.

/media/33/download/Untitled%20Diagram%20%281%29.jpg?v=1&inline=0

Execution of Payment Transaction using Payment Form (2D Secure Flow)

  1. Customer selects a product and submits an order.
  2. The merchant initiates the request of the Payment Form.
  3. Solid provides Merchant with the URL of the Payment Form.
  4. Merchant displays the Payment Form.
  5. The customer fills in and submits the Payment Form.
  6. Merchant requests purchase from Solid.
  7. Solid decides whether the transaction shall be executed via the 2D or 3D Secure flow (Scheme 3 refers to the 2D Secure payment, for the 3D Secure flow, please refer to Scheme 4). Solid sends the request to the Acquiring Bank to determine whether the transaction may be executed by the respective payment card.
  8. Acquiring Bank returns Solid the Verify Response defining whether the transaction is declined or approved*.
  9. Solid processes the Pay response and sends Callback request with Transaction status to the Merchant.
  10. Merchant displays the Payment Status Page to the Customer and responds to Solid that the transaction status is received.

     *The approved status means that the transaction is already executed

/media/11/download/UPD%20h2h%202d%20%281%29.jpg?v=1&inline=0

Execution of Payment Transaction using Payment Form (3D Secure Flow)

  1. Customer selects a product and submits an order.
  2. The merchant initiates the request of the Payment Form.
  3. Solid provides Merchant with the URL of the Payment Form.
  4. Merchant displays the Payment Form.
  5. The customer fills in and submits the Payment Form.
  6. Solid decides whether the transaction shall be executed via the 2D or 3D Secure flow (Scheme 4 refers to the 3D Secure payment, for the 2D Secure flow, please refer to Scheme 3). Solid sends the request to the Acquiring Bank stating that the transaction shall be executed according to the 3DS flow.
  7. Acquiring Bank responds with the ACS URL*.
  8. Solid sends Verify URL with ACS URL inserted.
  9. When a customer opens the URL, Solid receives Verify Request.
  10. The customer interacts with 3D Secure Page
  11. Merchant returns Solid the Return 3DS request.
  12. Solid requests the status of the 3D check from the Acquiring Bank
  13. Acquiring Bank returns Solid the Verify Response defining whether the transaction is declined or approved**.
  14. Solid processes the Verify Response and sends Callback request with Transaction status to the Merchant.
  15. Merchant displays the Payment Status Page to the Customer and responds to Solid that the transaction status is received.

     *The URL of the Access Control Server of the card-issuing bank that is returned in the reply to the request to check enrollment. This is where you must send the Payer Authentication Request message so that the customer can be authenticated;

     **The approved status means that the transaction is already executed.

/media/14/download/paymentForm%203DS%20%282%29.jpg?v=1&inline=0

Refunds

  1. Merchant requests Refund from Solid.
  2. Solid responds Merchant that the request is received. Solid sends the request to the Acquiring Bank to determine whether the Refund may be executed.
  3. Acquiring Bank returns Solid the Refund response defining whether the Refund is declined or approved.
  4. Solid processes the Refund response and sends Callback request with Transaction status to the Merchant.
  5. Merchant conducts the necessary actions on its side and responds to Solid that the Refund status is received.
/media/15/download/refunds.jpg?v=1&inline=0

Execution of Two-Step Payment Flow (Settle)

  1. Merchant requests authorisation for holding the Customer’s funds stating the interval (in hours) for its execution.
  2. Solid responds Merchant that the request is received. Solid sends the request to the Acquiring Bank to determine whether the authorisation is granted.
  3. Solid receives an Authorisation response from the Acquiring Bank.
  4. Solid processes the Authorisation response and sends Callback request with Transaction status to the Merchant.
  5. The merchant responds Solid that the Authorisation status is received.
  6. After the time interval stipulated in the Stage 1 Solid sends the request* to the Acquiring Bank to settle the transaction.
  7. Acquiring Bank returns Solid the Verify Response defining that the transaction is settled.
  8. Solid processes the Settle response and sends it (Callback request) to the Merchant.
  9. The merchant responds Solid that the transaction status is received.

    *Merchant can initiate settle of the partial transaction if the time interval has not expired yet. In this case, the remained amount will be automatically void.

/media/16/download/settle.jpg?v=1&inline=0

Execution of Two-Step Payment Flow (Void)

  1. Merchant requests authorisation for holding the Customer’s funds.
  2. Solid responds Merchant that the request is received. Solid sends the request to the Acquiring Bank to determine whether the authorisation is granted.
  3. Solid receives an Authorisation response from the Acquiring Bank.
  4. Solid processes the Authorisation response and sends Callback request with Transaction status to the Merchant.
  5. The merchant responds Solid that the Authorisation status is received.
  6. To initiate void operation Merchant sends Void request to Solid.
  7. Solid responds Merchant that the request is received and sends the Void request to the Acquiring Bank.
  8. Acquiring Bank returns Solid the Verify Response defining that the transaction is void.
  9. Solid processes the Void response and sends it (Callback request) to the Merchant.
  10. The merchant responds Solid that the transaction status is received.
/media/17/download/void.jpg?v=1&inline=0