The Create Sale Endpoint is applicable to both EU and US Acquiring Merchants.

The Sale transaction is used to create a sale for your consumer. You can create a credit sale or an ACH sale (ACH sales apply to US Merchants only).

A credit sale will charge a consumer's credit card. The consumer's credit card will be authorized immediately when the Sales request is received and will automatically settle/batch that same night. In other words, this one Sale request is just like running an AuthOnly and a Capture in one request.

You can postpone charging the consumer's credit card by providing a date in the 'ActivationDate' of your request. Doing so will delay the authorization and charge to the consumer's credit card until that future date.

An ACH sale (US Merchants only) will create an ACH transaction that will debit the consumer's bank account. ACH sales received prior to 3:00 PM EST will process overnight. ACH Sales received after 3:00 PM EST will process the following night.

📘

3D Secure Authentication using the Create Sale endpoint.

If the Merchant has integrated to ConnexPay's solution and has a signed contract to support 3D Secure using ConnexPay, the Create Sale endpoint must be combined with the BrowserData object to initiate 3D secure authentication.

In the event that the transaction requires a 3D secure device fingerprint, 3D secure cardholder challenge, or both, the Create Sale API must be called again once the 3DS status is complete by using the specified parameters on the GET 3DS Status API endpoint for authentication.

If a device fingerprint is required: secure authentication occurs behind the scenes so that the cardholder is not impacted. To successfully complete the device fingerprint, the webpage being used for payment must be configured to use an embedded iFrame. The iFrame is needed to complete the required redirection to the issuer's site. Use the redirectUrl and redirectUrlRequetPayload provided in the response to complete authentication. The response must occur within 10 seconds.

If a cardholder challenge is required: secure authentication must be completed by the cardholder. To successfully complete the challenge, the webpage being used for payment must be configured to use an embedded iFrame. This will be used to complete the required redirection to the issuer's site. Use the redirectUrl provided in the response to initiate the cardholder challenge.

Once a response is received, our callback API will be updated to show 3DS as complete. When the status is complete, the merchant will need to call the GET 3DS Status API route to receive the 3DS payload response. The parameter(s) included in the payload must be used to call the Create Sale route again and complete the transaction.

The new route to GET 3DS status once the auth is completed, as well as next steps including which parameters to include to complete the transaction, is located here: https://docs.connexpay.com/reference/get-3ds-status-group

For additional information about 3D Secure authentication, Click here .

Language
Authentication
OAuth2
Click Try It! to start a request and see the response here!