This guide outlines the necessary steps to connect your Pagos and Adyen accounts. For more information on connecting Pagos to other payment processors, see our Connecting Your Payment Processors to Pagos guide.
Be sure to configure all of your MIDs
The same reports need to be configured for all of the MIDs you connect to your Pagos account. This ensures the maximum data visibility necessary.
Log into your Adyen account to configure a set of automatic reports:
- Click the company name in the top-left corner of the page, then select the proper merchant account from the drop-down menu. This is vital, as these reports are enabled per merchant account and give us the ability to capture the maximum number of details. Save this Merchant ID for future use.
- Click Reports in the left-side navigation panel.
- For each of the following reports, click the name of the report to open its settings; click Manage report, then Automatic (generate on as schedule). Turn Automatic generation on and select .CSV for the File type:
- 3D Secure Authentication
- Aggregate settlement details
- Dispute transaction details
- Interchange and Scheme Fee report
- Payment Accounting Report
- Received payment details
- Settlement details
Follow the instructions outlined in Adyen's documentation to create a new API credential in your Adyen account for use in your Pagos account. For the Credential type, select Report service user.
Save the following information for future use:
- Under General settings, save the Username.
- Under Server settings, click the Basic Auth tab and save the Password.
At the bottom of the page, select Accounts by clicking the expansion arrow to the right of the section. This gives you options you can select from:
- Choose Company account and all associated merchant accounts to enable for all MIDs.
- Choose Only selected account groups and merchant accounts to manually select the the MIDs you want to enable for this data connection. If you choose this approach, you will need to update your selections here any time new MIDs are added.
🐘 (Remember, each MID needs to have the required reports enabled.) 🐘
When you're done, click Save changes.
To pull in Adyen data to Pagos, you'll need to add a new data source in your Pagos account:
- Log into your Pagos account.
- Click your profile icon in the navigation bar, then click Manage Account.
- Click the Data Sources tab.
- To add a new data source, click + Add Data Source.
- In the side panel that opens, click the Provider drop-down, then select Adyen.
- Fill in the following fields:
- Add any desired Tags to your data source.
- Click the save icon.
After you enter your Adyen details in the Data Sources page of your Pagos account and click Add, a pop-up will prompt you to create a webhook. Click Copy beside the destination URL, then click Ok.
Next, log into your Adyen account to create the webhook:
- In your Adyen control panel, go now to the company level view by clicking the company name in the top-left corner of the page. This will allow you to configure one webhook for all applicable MIDs at the company level.
- Click Developers, then click Webhooks.
- Click + Webhook in the top right of the page to create a new webhook. Keep in mind, you don't need to make any changes to your existing webhooks.
- Beside Standard notification, click Add.
- Click the pencil icon beside Server configuration, then paste the destination URL you copied from your Pagos account into the URL field.
- Select the MIDs to connect in your Adyen control panel. You can specify to include 'all' or individual MIDs. These should the same that were configured in step 1. You can find the list of available accounts under Merchant accounts.
- Under Additional Settings, click the pencil icon beside each of the following settings to expand these sections, then click the checkbox beside each of the following options:
- 3D Secure
- Include 3D Secure Result
- Include 3D Secure Version
- Include 3D Secure2 Challenge Flow Information Details
- Include Metadata in payment notification for 3D Secure payments (notifications are not sent from Pal)
- Include Raw 3D Secure Details Result
- Include Raw 3D Secure Result
- Add Acquirer Result
- Add Payment Account Reference
- Add Raw Acquirer Result
- Include Acquirer Error Details
- Include Acquirer Reference
- Include ARN
- Include Custom Routing Flagging
- Include the acquirer, acquirer account, raw response and response code of the (retry) attempts
- Include Card Bin
- Include card info for recurring contract notifications
- Include detailed Card BIN Information
- Include Extra Costs
- Include Funding Source
- Include Issuer Country
- Include Shopper Country
- Include Shopper Details
- Include Subvariant
- Include the co-brand card information
- Return AVS data
- Include Authorized Amount (dynamic zero auth)
- Include Shopper Interaction
- Include zero auth flag
- Add Capture Reference To Dispute Notification
- Include Device Type and Browser Information
- Include Dunning Project Data
- Include Gross Currency Chargeback Details
- Include notes in manual review notifications
- Include Risk Data
- Include Risk Experiment Reference (notifications are not sent from Pal)
- Include Risk Profile (notifications are not sent from Pal)
- Include Risk Profile Reference (notifications are not sent from Pal)
- Include the originalReference for CHARGEBACK_REVERSED notifications
- 3D Secure
- Click Test configuration to test the webhook, then click Save changes.
- Click the toggle next to your new webhook to turn it on.
Updated 4 months ago