Create a registration

post

https://testapi.continentalpay.com/rest/register

Registration API is used to register transaction to beused in payment creation at a later date.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Registration API is only supported in certain payment methods.

Credit Cards
Supported. Used to register card information to be captured at a later date.
Direct Debit
Not supported.
PIX
Not Supported
PayPal
Not supported.
Boleto
Not supported.

Registrations API is used to register credit card information for use in a future payment. Difference between Authorization API is that it does not have an amount to block for future deduction.

Below is the summary of the Registration API's use case.

Send a POST request to /rest/register with the parameters mentioned in the list below.
Redirect the end user to the returned URL.
End user inputs credit card data and gets redirected back to Merchant’s shop. In case of success, to success_url, in case of an error, to an error_url.
Transaction status should now be registered. Keep the transaction_id for use in original_transaction_id field in further requests.
Make a payment request Payment API. Fill original_transaction_id= with the ID from the Registration call above in the request body. Set recurring=1 if you intend to make recurring payments.

Body Params

api_key

string

required

API key of the merchant.

payment_type

string

required

Identifier for the payment method. See list of payment methods in the following link https://continentalpay.readme.io/reference/list-of-payment-methods.

order_id

string

required

Order ID of the payment. We suggest to use readable but unique value for this field.

recurring

int32

Defaults to 0

1 for recurring and 0 for non-recurring.

postback_url

string

HTTPs URL where you would like to receive webhook/postback notifications. E.g https://yourwebsite.com/postbacks

locale

string

Locale for the payment page. Only used in Credit Card payments where customer is redirected to our payment page. Find supported locales here.

additional_transaction_data

string

Any other random data that you would like to associate the transaction with.

address

string

Address of the customer.

address2

string

Supplementary address of the customer.

city

string

City of the customer.

postal_code

string

Postal code of the customer.

state

string

State of the customer.

country

string

required

2 letter ISO code of the country of the customer. E.g DE

first_name

string

First name of the customer.

last_name

string

Last name of the customer.

string

Email of the customer.

phone

string

Phone of the customer.

success_url

string

Success URL of your website to redirect customers to upon a successful payment. For payment methods that involve browser redirection such as credit card payments, these URLs are required. The following data is appended to the URL, which is used when redirecting back to the shop’s success or error URLs: order_id,transaction_id.

error_url

string

Error URL of your website to redirect customers to upon a failed payment. For payment methods that involve browser redirection such as credit card payments, these URLs are required. The following data is appended to the URL, which is used when redirecting back to the shop’s success or error URLs: order_id,transaction_id.

frame_origin

string

Domain of the website that will render our payment page. Only used for Credit Card payments when the redirect link will be rendered in an I-frame.

Response

200