Rapipago
Overview
Introduction
Rapipago is a payment method which allows to process payments in Argentinian pesos and US dollars by using vouchers in Argentina. This method supports purchases.
This article provides information about working with the Rapipago method: general insights are presented in the Overview section, while information about the actions required to process payments and perform other actions is presented in the sections that follow.
General information
Payment method type | point of sale payments |
---|---|
Payment instruments | vouchers |
Countries and regions | AR |
Payment currencies | ARS, USD |
Currency conversion | – |
One-time purchases | + |
Credential-on-file purchases | – |
Full refunds | – |
Partial refunds | – |
Payouts | – |
Chargebacks | – |
Notes |
|
Onboarding and access fee | refer to your ecommpay account manager |
Interaction diagram
Payment processing by using the Rapipago method involves the merchant's web service, one of ecommpay interfaces, the ecommpay payment platform, and technical facilities of the Rapipago service.
Operations support
Various platform interfaces can be used to process payments and perform operations using the Rapipago method. Purchases can be processed by using Payment Page, Gate and Dashboard (using payment links).
Processing scenarios
To perform a purchase by using the Rapipago method, you need to redirect the customer to the Rapipago service.
Figure: Purchase by using Payment Page
Figure: Purchase by using Gate
Purchases by using Payment Page
General information
To process a purchase through Payment Page by using the Rapipago method, the merchant's web service is required to send a request with all required parameters and signature to the ecommpay URL and receive a callback with the result. The full sequence and special aspects of purchase processing are provided below.
Figure: Purchase processing by using Payment Page: step-by-step description
- A customer initiates a purchase in the web service.
- The web service sends the request for opening Payment Page to the specified ecommpay URL.
- The request for opening Payment Page is sent to the payment platform.
- The payment platform receives the request and validates the required parameters and signature.
- Payment Page is generated based on the project and request parameters.
- Payment Page is displayed to the customer.
- The customer selects the Rapipago method.
- The requested payment form is displayed to the customer on Payment Page.
- The customer enters necessary personal data.
- Payment Page redirects the request to the payment platform for further processing.
- The payment platform processes the request and sends it to the Rapipago service.
- The request is processed on the Rapipago service side.
- The data for redirecting the customer to the Rapipago service is sent from the Rapipago service to the payment platform.
- The data for redirecting the customer is sent from the payment platform to Payment Page.
- The redirection link is displayed to the customer on Payment Page.
- The customer is redirected to the Rapipago service.
- The voucher with the instructions are displayed to the customer. The payment status
awaiting redirect result
remains until the customer completes the payment. Depending on the payment processing provider, the validity period of the payment voucher can either be 5 days (but a customer has 30 days to complete the payment by contacting to the bank) or 3 days. - The customer completes all required payment steps.
- The payment is processed in the kiosks service side.
- The kiosks service sends the payment result notification to the Rapipago service.
- The Rapipago service sends a notification about the result to the payment platform.
- The payment platform sends the payment result callback to the web service.
- The customer receives the payment result information from the web service.
Information about the formats of requests and callbacks used for processing payments by using the Rapipago method via Payment Page is presented further in this section; general information about working with the Payment Page API is presented in Interaction concepts.
Request format
There are several things you need to consider when using the Rapipago method:
- The following parameters required for any payment must be specified:
project_id
—project identifier obtained from ecommpay during integrationpayment_id
—payment identifier unique within the projectpayment_currency
—payment currency code in the ISO-4217 alpha-3 formatpayment_amount
—payment amount in the smallest currency unitcustomer_id
—customer identifier unique within the project
- The following parameters required for any payment must be specified:
project_id
,payment_id
,payment_currency
,payment_amount
,customer_id
. - The currency of payment can only be ARS or USD.
- Additionally, the following customer information should be specified:
customer_first_name
andcustomer_last_name
—first and last names of the customercustomer_email
—customer emailidentify_doc_number
—number of the customer's identity document, should consist of 7, 8 or 11 digits.
- If you need to have the payment form displayed with the Rapipago method selected, set the
force_payment_method
parameter torapipago
. - Additionally, any other parameters available for working with Payment Page can be used (details).
- After all target parameters are specified, generate a signature (details).
Thus, a correct request for opening the payment form using the Rapipago method must contain the project identifier, basic payment information (identifier, amount, and currency code), customer information and signature.
{ "project_id": 120, "payment_id": "580", "payment_amount": 10000, "payment_currency": "ARS", "customer_id": "customer1", "customer_first_name": "Guido", "customer_last_name": "Marques", "customer_email": "customer@example.com", "identify_doc_number": "12345678901", "signature": "kUi2x9dKHAVNU0FYldOcZzUCwX6R\/ekpZhkIQg==" }
Figure: Example of sufficient data in a purchase request
{ "project_id": 120, "payment_id": "580", "payment_amount": 10000, "payment_currency": "ARS", "customer_id": "customer1", "customer_first_name": "Guido", "customer_last_name": "Marques", "customer_email": "customer@example.com", "identify_doc_number": "12345678901", "signature": "kUi2x9dKHAVNU0FYldOcZzUCwX6R\/ekpZhkIQg==" }
Callback format
The Rapipago method uses the standard format for callbacks to deliver purchase results. For more information, see Callbacks.
The following is the example of a callback with information about a 500,00 ARS
purchase made in the 198
project.
Figure: Example of callback data indicating that the purchase has been processed
{ "project_id": 198, "payment": { "id": "TEST_Argentina_PC_2", "type": "purchase", "status": "success", "date": "2018-12-14T13:11:44+0000", "method": "rapipago", "sum": { "amount": 50000, "currency": "ARS" }, "description": "TEST_Argentina_PC_2" }, "customer": { "id": "1" }, "operation": { "id": 15, "type": "sale", "status": "success", "date": "2018-12-14T13:11:44+0000", "created_date": "2018-12-14T11:21:35+0000", "request_id": "7a1482b612d642a", "sum_initial": { "amount": 50000, "currency": "ARS" }, "sum_converted": { "amount": 50000, "currency": "ARS" }, "provider": { "id": 1167, "payment_id": "316", "date": "2018-12-14T13:07:15+0000", "auth_code": "" }, "code": "0", "message": "Success" }, "signature": "U+CDYj96jASxGI/KctgFQ4NzrZdOTaNUi+E/BBcR+g==" } }
The following is the example of a callback with information about a declined purchase.
Figure: Example of callback data indicating that the purchase has been declined
{ "project_id": 198, "payment": { "id": "TEST_15447012171635547", "type": "purchase", "status": "decline", "date": "2018-12-13T11:45:17+0000", "method": "rapipago", "sum": { "amount": 50200, "currency": "ARS" }, "description": "TEST_1544701217163" }, "customer": { "id": "1" }, "errors": [ { "code": 20101, "message": "Operation amount is great than max limit" } ], "operation": { "id": 4100000002248, "type": "sale", "status": "decline", "date": "2018-12-13T11:45:17+0000", "created_date": "2018-12-13T11:45:01+0000", "request_id": "fa22737fc8780b0b85b0", "sum_initial": { "amount": 50200, "currency": "ARS" }, "sum_converted": { "amount": 50200, "currency": "ARS" }, "provider": { "id": 1167, "payment_id": "" }, "code": 20101, "message": "Operation amount is great than max limit" }, "signature": "MMVpxlW/hsMybuF6u2SrRlSqNNslFp37JPhy4sdTpg==" }
Useful links
The following articles can be useful when implementing purchases via Payment Page:
- Interaction concepts—about the interaction with the payment platform by using Payment Page.
- Signature generation and verification—about the procedure of generating and verifying signatures in requests and callbacks.
- Payment models and statuses—about the types, processing models, and possible statuses of supported payments and operations.
- One-time one-step purchase—about processing of one-time one-step purchases by using Payment Page.
- Information of operations performing—about error and response codes that are used in the payment platform to record information about performing of operations.
Purchases by using Gate
General information
To process a purchase through Gate by using the Rapipago method, the merchant's web service is required to do the following:
- Send a request with all the required parameters and signature to the ecommpay URL.
- Receive an intermediate callback from the payment platform and redirect the customer to the Rapipago service.
- Receive the final callback from the payment platform.
The full sequence and special aspects of purchase processing are provided below.
Figure: Purchase processing by using Gate: step-by-step description
- A customer initiates a purchase by using the Rapipago method in the web service.
- The web service sends the request for processing the purchase by using Gate to the specified ecommpay URL.
- The payment platform receives the request.
- The payment platform validates the required parameters and signature in the request.
- The payment platform sends the response to the web service with information about the receipt of the request and its validity (details).
- The payment platform performs further processing of the request (with parameter consistency check) and sends it to the Rapipago service.
- The request is processed on the Rapipago service side.
- The Rapipago service sends the redirection data to the payment platform.
- The payment platform sends the callback with the redirection data to the web service.
- The redirection link is displayed to the customer.
- The customer is redirected from the web service to the Rapipago service.
- The voucher with the instructions are displayed to the customer. The payment status
awaiting redirect result
remains until the customer completes the payment. Depending on the payment processing provider, the validity period of the payment voucher can either be 5 days (but a customer has 30 days to complete the payment by contacting to the bank) or 3 days. - The customer completes all the payment steps required in one of the payment kiosks using the received voucher.
- The payment is processed on the kiosks service side.
- The kiosks service sends the payment result notification to the Rapipago service.
- The Rapipago service sends the payment result notification to the payment platform.
- The payment platform sends the payment result callback to the web service.
- The customer receives the payment result information from the web service.
Information about the formats of requests and callbacks used for processing payments by using the Rapipago method via Gate is presented further in this section. General information about working with the Gate API is presented in Interaction concepts.
Request format
There are several things you need to consider when sending purchase requests by using the Rapipago method:
- To initiate each purchase, send a separate POST request to the
/v2/payment/voucher/rapipago/sale
endpoint. This endpoint belongs to the group /v2/payment/voucher/{payment_method}/sale. - Each request must include the following objects and parameters:
- Object
general
—general purchase information:project_id
—project identifier obtained from ecommpay during integrationpayment_id
—payment identifier unique within the projectsignature
—request signature generated after all required parameters are specified (details—in the Signature generation and verification) (details)
- Object
payment
—payment information:amount
—payment amount in the smallest currency unitcurrency
—payment currency code in the ISO-4217 alpha-3 format
- Object
customer
—customer information:id
—customer identifier unique within the projectip_address
—customer IP address relevant for the initiated paymentfirst_name
—customer first namelast_name
—customer last nameemail
—customer email address- Object
identify
—information about the document which establishes identity:doc_number
—number of the customer's identity document, should consist of 7, 8 or 11 digits
- Object
- The currency of payment can be ARS or USD.
- Additionally, any other parameters included in the specification can be used.
Thus, a correct purchase request by using the Rapipago method must contain the project identifier, basic payment information (identifier, amount, and currency code), customer information, as well as signature.
{ "general": { "project_id": 580, "payment_id": "38202000002316", "signature": "h4ZxUifBXnBeF+iSR0K5OFdK0B9CjMCc2DbkDrk3qhLg==" }, "payment": { "amount": 10000, "currency": "USD", "description": "38202000002316" }, "customer": { "idv: "589256", "email": "Paul@mail.com", "first_name": "Paul", "last_name": "Marques", "identify": { "doc_number": "84887177100" }, "ip_address": "192.0.2.0" } }
Figure: Example of sufficient data in a purchase request
{ "general": { "project_id": 580, "payment_id": "38202000002316", "signature": "h4ZxUifBXnBeF+iSR0K5OFdK0B9CjMCc2DbkDrk3qhLg==" }, "payment": { "amount": 10000, "currency": "USD", "description": "38202000002316" }, "customer": { "idv: "589256", "email": "Paul@mail.com", "first_name": "Paul", "last_name": "Marques", "identify": { "doc_number": "84887177100" }, "ip_address": "192.0.2.0" } }
Formats of intermediate callbacks for customer redirection
Each payment made with the Rapipago method requires redirection of customers from the merchant's web service to the Rapipago service. To redirect a customer it is necessary to receive an intermediate callback from the payment platform and use the information included in the redirect_data
object. The format of such callbacks is standard (details), and the following objects and parameters are included in the redirect_data
object:
body
—object with data to be sent in the request bodymethod
—parameter specifying the HTTP method for sending the request (GET
orPOST
)url
—parameter containing a link for redirection
Figure: redirect_data example
"redirect_data": { "body": {}, "method": "GET", "url": "https://www.example.com/pay" }
Callback format
The standard format for callbacks is used to deliver purchase results from Rapipago. For more information, see Callbacks.
The following is the example of a callback with information about a 100,00 USD
purchase made in the 842
project.
Figure: Example of callback data indicating that the purchase has been processed
{ "project_id": 842, "payment": { "id": "EP8a3e-3e96", "type": "purchase", "status": "success", "date": "2019-06-03T12:09:38+0000", "method": "boleto", "sum": { "amount": 10000, "currency": "USD" }, "description": "" }, "operation": { "id": 1001313740, "type": "sale", "status": "success", "date": "2019-06-03T12:09:38+0000", "created_date": "2019-06-03T12:08:52+0000", "request_id": "46b8b94eabf", "sum_initial": { "amount": 10000, "currency": "USD" }, "sum_converted": { "amount": 10000, "currency": "USD" }, "provider": { "id": 1414, "payment_id": "9d7e3e16b6a5", "auth_code": "" }, "code": "0", "message": "Success" }, "signature": "hTnUho5lgWxu+wgKzmhLdj3e5d8PwovSQGtyFSH7OBlJ8bQ==" }
The following is the example of a callback with information about a declined purchase.
Figure: Example of callback data indicating that the purchase has been declined
{ "project_id": 842, "payment": { "id": "EP2ea6-f489", "type": "purchase", "status": "decline", "date": "2019-06-03T12:14:18+0000", "method": "boleto", "sum": { "amount": 1000, "currency": "EUR" }, "description": "" }, "operation": { "id": 2001313740, "type": "sale", "status": "decline", "date": "2019-06-03T12:14:18+0000", "created_date": "2019-06-03T12:13:38+0000", "request_id": "d5978bf20bae024", "sum_initial": { "amount": 1000, "currency": "EUR" }, "sum_converted": { "amount": 1000, "currency": "EUR" }, "provider": { "id": 1414, "payment_id": "D-30006-7729dab9-3782-4c0a-8192-840622f63f08", "auth_code": "" }, "code": "20000", "message": "General decline" }, "signature": "eL+OigWVAgeT85JjOOUIkg5KYy+MkG9SCynp47KzdImN3tAy0kA==" }
Useful links
The following articles can be useful when implementing purchases via Gate:
- Interaction concepts—about the interaction with the payment platform by using Gate.
- Signature generation and verification—about the procedure of generating and verifying signatures in requests and callbacks.
- Payment models and statuses—about the types, processing models, and possible statuses of supported payments and operations.
- One-time one-step purchase—about processing of one-time one-step purchases by using Payment Page.
- Information of operations performing—about error and response codes that are used in the payment platform to record information about performing of operations.
Analysis of payments results
To analyse information about payments made with the Rapipago method and other methods, you can use:
- Dashboard interface toolkit with various lists and analytic panels.
- Reports in CSV file format, available via the Reports section (one-time and periodically).
- Data in JSON format, sent by program requests to a specified URL available by using the Data API interface.
If you have any questions, refer to the documentation (Dashboard and Using Data API) and ecommpay technical support.