Create a registration

API key of the merchant.

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 of the payment. We suggest to use readable but unique value for this field.

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

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

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

Address of the customer.

Supplementary address of the customer.

City of the customer.

Postal code of the customer.

State of the customer.

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

First name of the customer.

Last name of the customer.

Email of the customer.

Phone of the customer.

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 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.

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.

Content type of the request body.