When you switch to BlueSnap, you can bring any existing shopper data, including their credit card details, along with you. There's no need to recollect payment details and recreate shopper records. We work with your current provider to securely migrate your data so you never have to handle it yourself. If you ever decide to leave, we will export your data to another PCI Level 1 provider.
You request a data export from your current provider to BlueSnap.
You contact your BlueSnap Implementation Specialist about importing data from your current provider.
We work with your current provider to ensure data is kept secure:
3.1. Your current provider verifies BlueSnap's Attestation of PCI Compliance (AOC), proving BlueSnap's compliance with the highest level of PCI security.
3.2. Your current provider generates an encrypted CSV file so no clear text data is present.
3.3. We provide SFTP login details to your current provider.
3.4. Your current provider securely transfers data to BlueSnap via SFTP.
We import your data into your BlueSnap account.
Once data migration is complete, BlueSnap will run an Account Update on all imported cards. There is a fee for this service but this benefits you by ensuring all cards are updated prior to any transactions.
You receive the data import results from BlueSnap.
You remap your shopper records according to their new IDs in BlueSnap.
If your current provider needs to verify BlueSnap's AOC, contact your BlueSnap Implementation Specialist. They will supply your current provider with this information.
We encourage you to provide us with as much information as possible about your shoppers. However, at a minimum, the following fields are required.
|Expiration month (MM)|
|Expiration year (YYYY)|
|Bank account number|
|Bank routing number|
|Account type |
For corporate accounts
- Each card should have its own row.
- Each card should be associated with a shopper by the ID (even if the shopper has multiple cards).
Your current provider can use our public key below to encrypt the CSV file.
-----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v2.0.22 (GNU/Linux) mQINBGBSIaUBEAC0R0Ac9vNzw64dvZIrlvrHllGGzGb1MvYh0znbrzfkXDyfgktV zV15oSsjkU6ysyZzx2pR0AdVRAi1sr6SOgQ91/nfnRMf0pDwGJgQzouxl2juXNaz lCj6JZ8i31bOexBMjegQWcL2hh7Uu6D3RyUazT8lsxEDdHXwwdzCergdn8o0MIQH gYieEPyo4KCizajiXIib7TtfMVJ7Dil3ADOnupX1E6XOmYgq1APFcovw1pX9UDKq 0qp03CWW1O9IwA/LSxWFHqUdvTz+6LNqD59smEzb6NMNmvE+tUbnWVR4SW9kGYwz QTVQJjJR5fxFX+E+3fn81a1DBjWVvkIR/WcbCnoFSZiO7zB/LSHZX9wlsdcXp3mn HVnHUOvBRDX5jUatf2HlkFA+czNuz/kZMCJ2uz4gmG00zHg50jK7C4RoWzxMSXIN cipEs2UpfMsu+aGzjCMxHI7rANpF6MuHdrrb+RRUeSvMwWNfk13xDY/hzuXZhpj7 Zp49ew5gVo6apQq43KPkbvDMdcTftfXjtWi9fzPtz2eMueVCdvol7VohMmc6p3m1 vDHiaXrbmDLaXlqg86h1+Mjwgnt1Hr+b61eo3MSUY7OC8qead/266nfLGJbPGnGc PvviMA5I3I0FEI/k+Q9E0GEqjtisNktKRT3+FwtqftFEpsAunC76l2vbDQARAQAB tB1CbHVlU25hcC1JVCA8SVRAQmx1ZXNuYXAuY29tPokCPwQTAQIAKQUCYFIhpQIb AwUJA8JnAAcLCQgHAwIBBhUIAgkKCwQWAgMBAh4BAheAAAoJEJk6iZYOeqxEVL4P /igPfCPt+mu9YTG88y/hUF2p5x//FHN0cvb7dBDG0CRjOGz0sGbFOc7Hca/SSTM2 pxrQKcpKEclskt8zdN1PeirUBnAbndh2BS9cY0vGKD5PnTdBQlwkkkMoSmekhWOx bUmL3jmdzjGFyJXQvyf5NlFi+qbz02/I2zOLcmEKUb7iEF+Ime1u8ix1BAjJGyPp 4LaNn0FwtmxLDlF7nbnPL2SFhgAHn/IKDvIQMQHxPri8BcwAeYT+49WXQURuvqQU CEKzv0wq094oIFOmTpVRnpXWrL/wsvJBHbS/iL7ROns20Xk/Xs4Bwa0vGiPf6UYY sjWL8eEfayTLLwNGtARlHO/oCNe0F4Dhgd/DNb6csSmCHcWGEpHtPIAk33TPHiZo j7GJpNd+xsrOStyHBhSL9bxOumuW4/EmEEPHz5fHpC0p3WtXtq+1tFZ7Wkon2c+J B3o1cbvZIBKMq+BzS01Cm85r0/hRFgbF4+qsr1JC9NT0wTeU+CFAXBP2TnQvsqXJ rrcqsnoNTXe3Nu+ZJEFPNGjNYUtw2bZOv6xIOcoHoviU/ycbbDG4dFm0Oi/VZ0q8 UCwrQGSSAm/zbdjkL8wWIEAezG10kv+FoY2ScMgqsHIJgqY/lBVql0Qc6lSw3EKR BVYcNwqsvKEHumK68rEY5GHystuLA8T9v8QgVLbQd54UuQINBGBSIaUBEADLhpdP 1OdpBW2CvpTs04dv5RszFmtyeKDlKgfoFk2TutwKxgDZaXzj1MrS6DQ2WI8nD0+j CVqdJ4oi0EgUQuzjTIhcC1HuqLr/83BccFlTDTs1bJrEbSWFV93D69FTNqbPvugy dck4Z71e8ndxjzNkBxoQd7hWy6MTsHTT5vwouMJ6ysB/856co68CkR9PQGxJeckV KWMYeWuYSah7X3uzSH3JayUZIqjw9FweQXanaxUKF4R2qpsB+DCFUZm3wgF+f19D dnbjsFnOfMbGDCFse5ReKcRN7xyxBC6BComTrcMCt/aFkRQQKWJlAzkdTJTaJc2e iKTPs0J/hOcsWX5nn33+nJ8pHFprCunWocGP5mNW2fJeKHgd+XYkySc/T5PMf4Jx IVHvdnsFRKTr1xtJU28d/Yr9PEtZWuqI00dwZPV3NyyTnQj6fDxyfVTds/dK29Wn FKZWviP7+uRBYwNZe+81Ey7aLImSR/75juiPgXzCVvJZOvHSXqoEiZIl28Y2/SFS YTNVGiyFe884e90RyGQLebwmc9nZAU0EkM4di5cSHxSYnjPUldFPclh6DM/3fjyq RY1J2+uNO4AtB16Xob0ERZSWAKILJ0BV0aj71qwlztXhqwU4SALKNZWLoTYwRMOO sWcQItrp9JgYKOFaBhsthnUzcapOfjIBqM1HSQARAQABiQIlBBgBAgAPBQJgUiGl AhsMBQkDwmcAAAoJEJk6iZYOeqxEFSUP/0Nj+pXM51bfK8OvLuCewLlGySTgukTH /PZyCmGWQVmDN4E0/NOj0fwN4XInvyNaXxEez3IYz3twY18ZeeTV8iIR8JKRHgLq aNR9QTuECQczLW2JUXL1fxRwRzcZdqOUqvAYZlDf5MAZzm60JjzirlGbIIN6gX1j KYZM5vqw67Y3qi6aCmAIEKiSXHnuzcSdrAAC70042gopAB+McS4CbMg7ulW4qndO tk3MxKEVkv0Aa92nmnhfG4896al3/kUo7qJGo59OIt4d+hd3YpGt6XHPFHd+7kla NMr2mo9cg2SakLD9XSuaupFtzbfVWAjb0cnVjHucie1vVdA0bu0SyxTHvoSQXW1G SrgJhp0pxpWOPVXx1NIcfwG7MSXfJrqqDtws8fSMAB6BpFh0M2rnfxfX2ahiw+17 +pwUGu61H8Fz0e9gzNQTETrtJ3OJpFSc2iemLgyvXsLNux2DIlIbpQwkAAfau8My 3lFJGR1miHGRspfpzhdZRyOkgePqbYRFIcGsFychPaQNcazJD2yW9IxOd844Ptwm Jny70u/LpF7Ny6fMTb8KuBNMZZVpd0SrQKSSO4hdiegSQc7eu7CwqWFvAUZE/i9F mA3bZVJKyUzcOFoobazI/oRAWD72GWUfwxTiK/8XdBvMqyKYaRN1RjMJ4YH6pyvL qggK00ngW7rJ =s0Ko -----END PGP PUBLIC KEY BLOCK-----
After your current provider has generated the encrypted CSV file, they need to notify us and provide the following information.
- IP address for the source of the data transfer so we can whitelist this information in our firewall.
- Contact information for another communication form, such as Skype or phone, through which we can share the SFTP login password.
After these details are received, we provide the SFTP login credentials.
After the data is imported into your BlueSnap account, you will receive two files containing the results (no sensitive card data is contained in either file). One file includes the IDs for each shopper that was successfully created in your BlueSnap account, as well as the last four digits for each of their cards. You will need to remap your shopper records using this file.
The second file contains the shopper records that failed to import and failure reasons. You can use this file to investigate the errors and decide if you would like to retry importing these records.
Using the results file from the data import, you need to remap your shopper records according to their new IDs in BlueSnap. For example, your shopper John Doe has an ID of 12 on your side, which corresponds to an ID of 5332 from your previous provider. Now, John Doe has an ID of 9033 in your BlueSnap account. You need to update your database to associate John Doe's record with his new ID of 9033 in BlueSnap.
Working with subscriptions?
Use our Subscription Engine to set up plans and subscriptions.
If you decide to leave, we securely export your data to another PCI Level 1 provider, ensuring that you don't have to handle the sensitive data yourself.
You inform your BlueSnap Account Manager or Merchant Support that you want to export your data to your new provider.
We verify your new provider's Attestation of PCI Compliance (AOC), proving their compliance with the highest level of PCI security.
We obtain your new provider's public encryption key.
We generate an encrypted CSV file, using your new provider’s public encryption key so no clear text data is present.
We transfer the encrypted file to your new provider via SFTP.
You work with your new provider on next steps.
The export of your shopper records is an encrypted CSV file. Each card has its own row and is associated with a shopper by the shopper's ID in your BlueSnap account.
Exporting existing subscriptions and importing them to your new provider is not supported. You can use the Reporting API or send a Retrieve all Subscriptions request to get a list of all your active subscriptions in BlueSnap. You can then work with your new provider to set up subscriptions using their capabilities.
Updated 10 months ago