Integrate iPaaS.com with BlueSnap to collect invoice payments through BlueSnap Checkout pay links: the integration makes a pay link for each invoice FROM iPaaS.com, writes it back onto the invoice, and brings card payments, refunds and expiries back TO iPaaS.com.
How to Connect
Prerequisites
Before setting up the BlueSnap integration in iPaaS.com, ensure the following in your BlueSnap Merchant Portal:
API credentials: Create them under Settings > API Settings in the BlueSnap Merchant Portal (see BlueSnap's How to get your BlueSnap API credentials). Enter an API password, then select Request API credentials; BlueSnap shows the new key under API User Key. These are not the username and password you use to sign in to the Merchant Portal.
Use the primary API credentials: The integration reads BlueSnap's Transaction Detail report, retrieves transactions and creates BlueSnap Checkout pay links. BlueSnap's secondary credentials carry only the permissions you grant (such as Reporting and Retrieve Transactions), and a credential without the permission a call needs is refused with BSNP-AUTZ-1001. If you use a secondary credential, grant it at least Reporting and Retrieve Transactions, and contact BlueSnap Merchant Support for any further permission it needs.
Authorized IPs: BlueSnap only accepts API calls from the addresses listed under Authorized IPs on the API Settings page. This list belongs to your BlueSnap account's API settings as a whole, not to one credential (BlueSnap: secondary credentials inherit the primary credentials' authorized IPs). BlueSnap allows up to 15 addresses or a subnet, and once at least one address is saved the list can never be emptied, so add only addresses you intend to keep. Do not select Disable IP Checking on a production account; BlueSnap advises against it unless you cannot provide a static IP address. Add both iPaaS.com outbound addresses:
20.98.221.25
69.61.66.130
BlueSnap Checkout: The integration creates BlueSnap Checkout (hosted payment page) pay links, so your BlueSnap account must be able to use BlueSnap Checkout. BlueSnap's Hosted Pages guide notes that setting a pay link lifetime can require a privilege on your account. If BlueSnap refuses pay link requests with BSNP-AUTZ-1001, ask BlueSnap Merchant Support to confirm that BlueSnap Checkout and the pay link lifetime privilege are enabled for your API credentials.
Card payments: This version of the integration supports card payments. Turn off other payment methods on your BlueSnap Checkout so payers pay by card.
Configuration Details
API Url: BlueSnap's API address for your account's environment. Production: https://ws.bluesnap.com. Sandbox: https://sandbox.bluesnap.com (BlueSnap: Sandbox & Production Environments).
Example: https://ws.bluesnap.com
API Username: The API User Key shown on BlueSnap's Settings > API Settings page.
Example: YourAPIUserKey
API Password: The API password you entered when you requested the API credentials.
Example: YourAPIPassword
Configure Subscription Settings
Navigate to the BlueSnap subscription settings in iPaaS.com and provide the following information:
Field | Description | Required | Example |
Name | A unique name for identifying the subscription. | Yes | BlueSnap Integration |
Versions | The iPaaS.com BlueSnap integration version to use. | Yes | 1.0.0 |
API Url | BlueSnap's API address: https://ws.bluesnap.com for production or https://sandbox.bluesnap.com for a sandbox account. Blank uses the production address. A bare host name is read as an https address, and a trailing /services/2 is accepted. It must be an https address, or the connection is refused with BSNP-VALD-1009. | Yes | |
API Username | The API User Key of your BlueSnap API credentials. | Yes | YourAPIUserKey |
API Password | The password of your BlueSnap API credentials. | Yes | YourAPIPassword |
Payment Success Url | The page the payer lands on after paying. It must be a web address (https:// or http://). Every pay link needs a success page: when this setting is blank and the invoice does not supply its own, the invoice is refused with BSNP-VALD-1008. | Conditional: required unless your FROM iPaaS.com mapping supplies a success page for every invoice | |
Payment Cancel Url | The page the payer lands on if they select Cancel on the BlueSnap pay page. It must be a web address (https:// or http://). Blank uses the Payment Success Url. | No | |
Pay Link Lifetime Days | How many days a new pay link can be paid, when the invoice does not set its own expiry date. A whole number from 1 to 365; blank uses 30 days. | No | 30 |
Reconciliation Days | How far back, in days, the reconciliation poll looks for invoices to check (see Reconciliation Days below the table). A whole number from 1 to 365; blank uses 60 days. | No | 60 |
Pay Page Url | The BlueSnap page a pay link opens. Leave it blank to use BlueSnap's own Checkout page for the API Url's environment (https://pay.bluesnap.com/checkout for production, https://sandpay.bluesnap.com/checkout for sandbox). When set, it must be an https address on BlueSnap's Checkout host for the API Url's environment (pay.bluesnap.com or sandpay.bluesnap.com); any other host is refused, so pay links can never send payers to a site that is not BlueSnap's. | No | (blank) |
Reconciliation Days. The poll checks the invoices whose iPaaS.com transaction changed within this window (making or renewing a pay link counts as a change).
Paid, refunded and cancelled invoices drop out once their last change is older than the window, so a late refund or a payment on a cancelled invoice still comes back within it.
Keep it longer than Pay Link Lifetime Days and than any expiry date your mapping sets, so an invoice is still checked for as long as its link can be paid.
An invoice outside the window can still be brought up to date with a Manual Sync.
How settings are checked. Each time the integration connects, it checks the settings before calling BlueSnap. Any of these stops the connection:
A required setting is blank (BSNP-AUTH-1001).
The API Url is not an https address (BSNP-VALD-1009).
An optional setting cannot be used (BSNP-VALD-1010): days outside 1 to 365 or not a number, a URL that is not a web address, or a Pay Page Url that is not on BlueSnap's Checkout host.
A blank optional setting is never a problem; it simply uses its default. A refused connection is reported where every error is, under Dashboard / Integration Monitoring / Error Logs, with iPaaS.com's message "Unable to connect to subscription". When you see it there, check each setting against the table above, and then the API credentials.
When changes take effect. A changed Payment Success Url, Payment Cancel Url or Pay Link Lifetime Days applies to the next pay link made; links already sent keep the pages and expiry they were made with. A changed Reconciliation Days applies from the next poll.
Before going live. Pay one small live invoice through its pay link and confirm the payment comes back onto the invoice in iPaaS.com before sending pay links to your customers.
Authentication Methods
Method: BlueSnap API Credentials (Basic Authentication)
In the BlueSnap Merchant Portal, create your API credentials and add the iPaaS.com addresses to Authorized IPs (see Prerequisites above).
Navigate to the BlueSnap subscription settings in iPaaS.com.
Enter the API Url, API Username (your API User Key) and API Password.
Save the configuration.
iPaaS.com sends the API Username and API Password in a Basic Authentication header on every call to BlueSnap, as BlueSnap's Authentication & Headers documentation requires; there is no separate sign-in or consent step. To check the connection, the integration reads today's BlueSnap Transaction Detail report (at most once every 10 minutes for the same credentials), which proves the credentials, the Authorized IPs entry and the Reporting permission in one call, and reads your BlueSnap merchant id from it, so you never enter it. A refused credential is reported as BSNP-AUTH-1002.
Changing credentials. To rotate the API password, update it in BlueSnap's API Settings, then enter the new value in API Password in iPaaS.com. The next connection checks the new credentials.
Initialization Support
Currently, initialization is not supported for BlueSnap in iPaaS.com. All data synchronization and mappings must be configured manually during the integration process.
Payments come back TO iPaaS.com by the reconciliation poll, which is the integration's intended trigger. Under Dashboard / Integration Monitoring / Events, add an event of type Webhook (Poll Request) for this BlueSnap subscription with scope invoice/poll and a 15-minute schedule; no payments, refunds or expiries come back until this event is scheduled. Leave the invoice/payment webhook off. An individual invoice can also be brought up to date at any time with a Manual Sync.
Throttling
Throttling ensures that the BlueSnap API isn't overwhelmed by excessive API calls, preserving system performance during heavy data transfers.
While the throttling fields are required, the values are pre-populated by the integration settings. For more details, refer to Subscription Configuration – Edit.
BlueSnap does not publish fixed call limits; it answers with an HTTP 429 or 503 error when an account exceeds its authorized thresholds (BlueSnap: Error Handling Overview). When that happens, the integration holds the transfer (BSNP-EXTN-1007) and retries it after 60 seconds (or after the wait BlueSnap names, if its answer includes one); nothing is lost. The reconciliation poll stops at the invoice it reached and the next run continues from there.
Related Documents