Integration scenarios

The system allows for different integration scenarios, ranging from the very basic to almost limitless functionality, depending on the requirements.

Payment form with email notifications on accepted payments

If you need to check transactions before payments and register them after payment:

  • Add the widget script to your website;
  • Set up email notification address in your Merchant account to receive notifications.
Payment form with payment registration

If you need to register transactions in your system, but you do not need to check them before paying, you should do the following:

  • Add the widget script to your website;
  • Create payment registration
    • Create a script for processing Pay notifications, for example
      https://site.com/webhooks/cloudpayments/pay
    • Configure the transaction registration logic and response in JSON format
    • Turn on the sending of Pay notifications in your Merchant account
Payment form with verification and payment registration

If you need to register transactions in your system, you should do the following:

  • Add the widget script to your website;
  • Setup payment verification
    • Create a script for processing Check notification, for example
      https://site.com/webhooks/cloudpayments/check
    • Configure the transaction verification logic and response in JSON format
  • Setup payment registration
    • Create a script for processing Pay notifications, for example
      https://site.com/webhooks/cloudpayments/pay
    • Configure transaction registration logic and response in JSON format
  • Turn on Check and Pay notifications in your Merchant account
Recurring (one-click payments)

If you need to store card data on payment gateway for subsequent paying in one click without entering card data and without 3-D Secure, you can do the following:

  • Your site must have authorization by the users with access to a personal account
  • With the first transaction, ask the user to connect a card with the account, so that they won’t need to enter the data again with each payment.
    CloudPayments Recurring
    If the user agrees, after payment, in their account, store the card mask (type of 4 last digits), and the token. Example of card and token are returned by the system in Pay notification and through API. You need to send user identifier in AccountId parameter to receive the token.
  • In subsequent payments, offer the user to pay with the previously registered card
    CloudPayments Recurring
    If the user selects a previously registered card you can use a token-based scheme via API.
  • Allow the user to control the cards which are connected CloudPayments Registered cards
    If the user does not want to use a connected card anymore, delete the mask and token from their profile.
  • Create a payments history page, which contains at least payment date and amount.
Recurrent (subscription payments)

If you need your users to pay you based on a subscription model, on a schedule basis, you can do the following:

  • On your site you need user authorization with access to their personal account.
  • Before creating a subscription plan, inform the user about the subscription plan, frequency of payments, and offer them to enter their card information.
    CloudPayments Recurrent
  • In accordance with your business process, create an authorization for 1 euro to check the card or payment for the first term of the subscription.
  • Receive the card token through API or Pay notification and create a plan of recurring payments. You need to send user identifier in AccountId parameter to receive the token.
  • Subscribe for Fail and Recurrent notifications. After receiving a notification about an unsuccessful payment, inform the user that they need to check their card. After subscription ends or is cancelled, stop providing your services to the user.
  • Create a payments history page, which contains at least payment date and amount.