Credentials
When setting up ACI Worldwide in the dashboard, configure the following credentials, which are obtained from ACI Worldwide merchant dashboard:Entity ID
The entity required to authorize the request. This should be the channel entity identifier. In case channel dispatching is activated then it should be the merchant entity identifier.Access token
The access token can be found under Administration -> Account data -> Merchant / Channel InfoBase URL (optional)
The base URL to use for API requests. If no Base URL is provided then the following defaults are used:| Environment | Base URL |
|---|---|
| sandbox | https://eu-test.oppwa.com/ |
| production | https://eu-prod.oppwa.com/ |
Connector configuration
After setting up your ACI Worldwide connector in the dashboard, configure how transactions are routed to it. Choose one of the following options:- Using Flow - Configure ACI Worldwide as the target connector in Flow to automatically route card transactions to this connector
- Using the API - Explicitly set the
payment_service_idparameter to the ACI Worldwide connector ID when creating transactions. This overrides any Flow routing rules.
Capabilities
Supported countries
Supported currencies
Integration
To accept card payments with ACI Worldwide, you need to use one of Gr4vy’s client-side integration methods. Due to PCI compliance requirements, card data should never be sent directly to your servers. You can integrate using:- Embed - A pre-built, customizable payment form that handles the complete payment flow
- Secure Fields - Embed card input fields for building custom payment forms while maintaining PCI compliance
- Mobile SDKs - Native SDKs for iOS, Android, React Native, and other platforms
Testing
For testing in sandbox environments, you can use standard test card numbers. ACI Worldwide supports industry-standard test cards for simulating different transaction scenarios: Successful transactions:- Visa:
4111 1111 1111 1111 - Mastercard:
5555 5555 5555 4444 - American Express:
3782 822463 10005