Integration CloudPayments (Cloudpayments) and Albato (Albato)

Connection in 5 minutes, 30 days on tests, try.

Accepted webhooks
Done actions
New clients

Try 30 days free

Free Turnkey setting, Instructions.

What data can be transmitted from: from_Service to: to_Service

Important: Please note that the presence of events and actions between the two services does not guarantee a solution your task - the available events and actions may not connect with each other in the way you need.

If you cannot independently determine whether these events and actions will be able to solve your problem; contact support or use the Full construction setting.

Events c CloudPayments

Click on the name of the event to see the available fields.

API documentation — here.

Description

Not

Available fields
Id Name
TransactionId Transaction number in the system
Amount Payment amount
Currency Currency: RUB/USD/EUR/GBP
PaymentAmount Payment amount
PaymentCurrency Currency: RUB/USD/EUR/GBP
DateTime Date/time of payment creation in UTC time zone
CardFirstSix The first 6 digits of the card number
CardLastFour The last 4 digits of the card number
CardType Card payment system: Visa, Mastercard, Maestro or MIR
CardExpDate The validity period of the card in MM/YY format
TestMode The sign of the test mode
Status Payment status in case of successful completion: Completed — for single—stage payments, Authorized - for two-stage payments
OperationType Operation Type: Payment/Refund/CardPayout
GatewayName The identifier of the acquiring bank
InvoiceId Order number
AccountId User ID
SubscriptionId Subscription ID (for recurring payments)
Name Name of the cardholder
Email Payer's e-mail address
IpAddress The payer's IP address
IpCountry Two-letter code of the payer's country of residence according to ISO3166-1
IpCity The payer's city of residence
IpRegion The payer's location region
IpDistrict The payer's location
Issuer Name of the issuing bank of the card
IssuerBankCountry Two-letter country code of the card issuer according to ISO3166-1
Description Purpose of payment
Data An arbitrary set of parameters passed to the transaction
Token Card token for repeated payments without entering details
TotalFee The value of the total commission
CardProduct Type of card product
PaymentMethod Payment method Apple Pay or Google Pay
FallBackScenarioDeclinedTransactionId The number of the first unsuccessful transaction
+ You can add your fields that are in webhuk.

Description

Not

Available fields
Id Name
TransactionId Transaction number in the system
Amount Payment amount
Currency Currency: RUB/USD/EUR/GBP
PaymentAmount Payment amount
PaymentCurrency Currency: RUB/USD/EUR/GBP
DateTime Date/time of payment creation in UTC time zone
CardFirstSix The first 6 digits of the card number
CardLastFour The last 4 digits of the card number
CardType Card payment system: Visa, Mastercard, Maestro or MIR
CardExpDate The validity period of the card in MM/YY format
TestMode The sign of the test mode
Status Payment status in case of successful completion: Completed — for single—stage payments, Authorized - for two-stage payments
Reason Payment problem
ReasonCode The problem code
OperationType Operation Type: Payment/Refund/CardPayout
GatewayName The identifier of the acquiring bank
InvoiceId Order number
AccountId User ID
SubscriptionId Subscription ID (for recurring payments)
Name Name of the cardholder
Email Payer's e-mail address
IpAddress The payer's IP address
IpCountry Two-letter code of the payer's country of residence according to ISO3166-1
IpCity The payer's city of residence
IpRegion The payer's location region
IpDistrict The payer's location
Issuer Name of the issuing bank of the card
IssuerBankCountry Two-letter country code of the card issuer according to ISO3166-1
Description Purpose of payment
Data An arbitrary set of parameters passed to the transaction
Token Card token for repeated payments without entering details
TotalFee The value of the total commission
CardProduct Type of card product
PaymentMethod Payment method Apple Pay or Google Pay
FallBackScenarioDeclinedTransactionId The number of the first unsuccessful transaction
+ You can add your fields that are in webhuk.

If you haven't found the right event, but the service has the right webhook, then use the universal connector "Including webhuk". It will be possible to tie the logic of bundles to any field that comes in the webhook.

Actions in Albato

Click on the name of the action to see the available fields.

API documentation — No.

Request fields
Id Name
body Request Content
Answer fields
Id Name