Is gateway reporting the same as Acru Checkout?
No. Reporting for an existing gateway and building on Acru’s custom checkout are separate integration paths.
Traditional gateway: NMI or Authorize.net
With this setup, payments continue through the merchant’s NMI or Authorize.net gateway. Acru is the reporting layer where the merchant can view the connected activity. Connecting a gateway does not replace the processor, change funding terms, or automatically add custom-checkout features.
Confirm the gateway account, credentials, reporting permissions, and data coverage during onboarding. Never share secret gateway keys in a support message.
Acru custom checkout
The custom-checkout path uses Acru’s payment interfaces and API-led flows. Hosted, Embedded, and API are implementation options to discuss for that product, not automatic upgrades to a traditional gateway connection.
Wallet infrastructure, smart-contract components, and custom-checkout risk services belong to this path only when included in the approved implementation. They are not prerequisites for viewing NMI or Authorize.net reporting.
What to confirm before launch
- Which of the two paths your account will use
- Who processes the payment and who supplies the reporting data
- Which account, transaction states, and reporting fields are connected
- Which features are ready for use versus planned work
- What your team must test before using live payments
Partner availability
A provider appearing in an integration directory does not mean every account can use every feature. New processor connections, payout services, and risk products require their own approved scope. Confirm availability with Acru before designing a customer flow around them.