Breadcrumbs

REST API Hosted Forms

Streamline checkout flows by embedding payment method selection directly into your website while leveraging secure, hosted forms.

Key advantages:

  • Design your own payment method selector UI/UX

  • Sensitive customer data remains entirely with NEXI's system significantly reducing your PCI-DSS compliance responsibilties and associated costs

  • Automatic validation and error management

  • Adjust the layout, colors and branding elements to align with your website's appearance for Cards and Direct debit

Payment flow

Forms hosted

Applicable payment methods: Cards and SEPA Direct Debit

  1. Customer proceeds to checkout on your online store.

  2. Your frontend requests the payment page to the backend.

  3. Your backend makes a Create payment call with paymentMethods.integrationType=HOSTED to NEXI.

  4. NEXI responds with HTTP 202 response code and a redirect URL to your backend.

  5. Your backend orchestrates the browser to redirect the UI to the redirect URL.

  6. Customer is redirected to payment form hosted by NEXI.

  7. Customer enters the details and completes payment.

  8. Upon completion, customer is redirected to the return URL that was submitted by you during Create payment call (urls.return) with payId in the query parameters.

  9. Browser fetches the return URL hosted by your backend.

  10. Backend makes a GET Payment details call with payId to retrieve the responseCode of the payment.

  11. NEXI responds with the responseCode of the payment along with other parameters.

  12. Your backend returns a success or a failure page based on the responseCode of the payment.

Forms hosted by APM (Alternate Payment Method Providers)

  1. Customer selects a payment method and proceeds to checkout on your online store.

  2. Your frontend requests the payment page to the backend.

  3. Your backend makes a Create payment call with paymentMethods.integrationType=HOSTED to NEXI.

  4. NEXI makes a payment request to the APM provider

  5. APM provider responds with redirect URL

  6. NEXI responds with HTTP 202 response code and a redirect URL to your backend.

  7. Your backend orchestrates the browser to redirect the UI to the redirect URL.

  8. Customer is redirected to payment form hosted by APM provider.

  9. Customer enters the details and completes payment.

  10. APM provider redirects the customer to NEXI's callback URL that was submitted in step 4.

  11. Browser requests callback URL to NEXI.

  12. NEXI communicates with APM provider to confirm the responseCode of the payment.

  13. Upon completion, customer is redirected to the return URL that was submitted by you during Create payment call (urls.return) with payId in the query parameters.

  14. Browser fetches the return URL hosted by your backend.

  15. Backend makes a GET Payment details call with payId to retrieve the responseCode of the payment.

  16. NEXI responds with the responseCode of the payment along with other parameters.

  17. Your backend returns a success or a failure page based on the responseCode of the payment.

Supported payment methods

Refer to Payment methods overview for the list of supported payment methods on Hosted forms.