Technical Integration Review

To submit a project for review, you will be asked to fill out a basic Technical Integration Checklist.

The checklist will help you ensure that your integration matches basic integration requirements.

To help us facilitate the Integration Review, please provide the following:

• A link where Paymentwall is integrated on your website/application and where we can access the integration.
  This can be your test environment. If this is a mobile application, please provide a downloadable link to your application.
• A lest account that we can use to access the integration.

As a next step we will review the integration following the checklists below. Merchants are encouraged to go through this checklsit themselves to facilitate the review and go live quickly.

Checklist for Checkout API, Widget API

• Integrate a Paymentwall using iframe or redirect. It should be accessible on your website/application.

• User ID (uid) must be persistent and unique per user.

• Make a test payment using Test Payment Method.

• If subscriptions are used:
  • Your website should clearly indicate subscription terms.
  • Cancellation and refund policy is clearly accessible and visible in the website.

• Set up a Pingback listener on your server.

• You need to respond ok to the following pingback types.
  • Confirmation pingback with type=0.
  • Negative pingback with type=2.

• Pingbacks with duplicated ref parameter should be discarded to avoid delivering the same product twice for a customer.

• Pingbacks with wrong signature should be discarded.

• Pingbacks are being tracked and the product is being delivered.

• If goods/services are not delivered instantly, Delivery Confirmation API implementation is required.

• Industry-Specific Requirements are met, for example for E-commerce businesses.

Checklist for Brick Direct API

Below is the checklist for merchants who are using Brick Direct API.

• Payment page must be loaded via HTTPS.

• Client-side tokenization using Brick.js, fingerprint is included in Brick requests.

• 3D secure payment step is implemented.

• Your servers does NOT receive/handle customer’s CC data.

• If subscriptions are used:
  • Your website should clearly indicate subscription terms.
  • Cancellation and refund policy is clearly accessible and visible in the website.

• Set up a Pingback listener in your server.

• You need to respond ok to the following pingback types.
  • Confirmation pingback with type=0.
  • Negative pingback with type=2.
  • Transaction pending pingback with type=200.
  • Transaction accept pingback with type=201.
  • Transaction decline pingback with type=202.

• Pingbacks with duplicated ref parameter should be discarded to avoid delivering the same product twice for a customer.

• Pingbacks with wrong signature should be discarded.

• Pingbacks are being tracked and the product is being delivered.

• If goods/services are not delivered instantly, Delivery Confirmation API implementation is required.

• Industry-Specific Requirements are met, for example for E-commerce businesses.

Relevant topics

Website Standards.