- Get Started
- Guides
- Integrations
- References
- API Reference
- Basic Payment
- Forex
- Authentication
- Card Account
- Apple Pay
- Virtual Account
- Bank Account
- Token Account
- Customer
- Billing Address
- Merchant Billing Address
- Shipping Address
- Merchant Shipping Address
- Corporate
- Sender
- Recipient
- Merchant
- Marketplace & Cart
- Airline
- Lodging
- Passenger
- Tokenization
- Recurring Migration
- 3D Secure
- Custom Parameters
- Async Payments
- Webhook notifications
- Job
- Risk
- Point of Sale
- Response Parameters
- Card On File
- Chargeback
- Result Codes
- Payment Methods
- Transaction Flows
- Regression Testing
- Data Retention Policy
- Release Notes
- API Reference
- Support
ConnectIn Workflow
Quick links
The diagrams in the section only represent the interactions between Shopper, Merchant, ACI and the Integrator. The messages exchanged between the Integrator and the APM/Acquirer are only partially represented.
Credit Cards
Server-to-Server
COPYandPAY
Virtual Account
Server-to-Server
This workflow allows the integration of APMs that require redirections and intermediate status for deferred payments, for which the final status is not known immediately after the shopper concludes the process at the APM.
- Status-update notifications Integration Guide-Async Notifications (Integrator --> ACI) should be preferably done using
notificationURL
rather than sending the status together with the shopper redirection usingshopperResultUrl
. In the second case, if the shopper redirection fails, the status would be never changed at ACI platform. - Notice that the parameters
shopperResultUrl
andnotificationUrl
are generated in and point to the ACI platform. TheshopperResultUrl
with the same name sent by the merchant is not forwarded to the middleware. The integrator redirects the shopper to ACI after the payment is finished at the APM and ACI will perform the redirection to the merchant. - ECI
- verificationId
- xid
- Directory Server transaction ID - threeDSecure.dsTransactionId
- 3D Secure version - threeDSecure.version
- 3DS Requestor Challenge Indicator - threeDSecure.challengeIndicator
- ACS Challenge mandate indicator - threeDSecure.challengeMandatedIndicator
- Exemption flag - threeDSecure.exemptionFlag
- Authentication Type - threeDSecure.authenticationType
- ACSTransactionID
- Child links
- Eci – threeDSecure.eci
- VerificationId - threeDSecure.verificationId
COPYandPAY
.Prepayment/Invoice/Online-Transfer – Receipt workflows
Server-to-Server
COPYandPAY
3D Secure
3DS 1.0
3DS 1.0 fields sent to the integrator in the PIM:
3DS 2.0
3DS 2.0 fields sent to the integrator in the PIM:
Create the payment form
For more details about these fields visit https://docs.aciworldwide.com/support/3d-secure-2.0-guide