{"_id":"59dfa8f45c0bae001c2e8af6","category":{"_id":"59dfa8f45c0bae001c2e8ae9","version":"59dfa8f45c0bae001c2e8ae8","project":"57336fd5a6a9c40e00e13a0b","__v":0,"sync":{"url":"","isSync":false},"reference":false,"createdAt":"2015-10-01T16:04:11.135Z","from_sync":false,"order":0,"slug":"welcome","title":"Quickstart"},"parentDoc":null,"project":"57336fd5a6a9c40e00e13a0b","user":"560d5913af97231900938124","version":{"_id":"59dfa8f45c0bae001c2e8ae8","project":"57336fd5a6a9c40e00e13a0b","__v":1,"createdAt":"2017-10-12T17:40:04.535Z","releaseDate":"2017-10-12T17:40:04.535Z","categories":["59dfa8f45c0bae001c2e8ae9","59dfa8f45c0bae001c2e8aea","59dfa8f45c0bae001c2e8aeb","59dfa8f45c0bae001c2e8aec","59dfa8f45c0bae001c2e8aed","59dfa8f45c0bae001c2e8aee","59dfa8f45c0bae001c2e8aef","59dfa8f45c0bae001c2e8af0"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"3.23. Release","version_clean":"8976.0.0-Basics","version":"8976-Basics"},"__v":0,"updates":[],"next":{"pages":[],"description":""},"createdAt":"2015-10-15T15:11:24.290Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":5,"body":"Let's walk through some key items you'll want to handle before you launch, so that you can achieve frictionless checkout and maximize your payment conversions. Then you can start getting paid!\n\n##Prepare for launch\n\n###1. Set up your statement descriptor\nThe statement descriptor (or \"soft\" descriptor) is the description that shoppers see on their credit card or bank statement for each transaction. The descriptor typically includes the business name and a shopper support phone number. It can also include information such as the product name.\n\nYou should set a default statement descriptor for your account, and you can also define descriptors dynamically per transaction.\nSee [Statement descriptor](doc:statement-descriptor).\n\n###2. Understand your fraud prevention options \nBlueSnap partners with [Kount](http://www.kount.com/) to offer three levels of fraud prevention services: Managed, Merchant Configurable, and Enterprise. Every merchant is automatically enrolled in the Managed level of fraud prevention.\n[Learn more](doc:fraud-prevention) about what this means and whether an enhanced level of fraud prevention may be right for you.\n\n###3. Enable real-time event tracking with IPNs\nInstant Payment Notifications (also known as Webhooks) send real-time notifications about transaction events directly to your system. These notifications include basic information about the transaction, such as price, product, and shopper information. IPNs are sent in HTTP POST format to a unique URL that you define.\nSee [IPNs (Webhooks)](doc:webhooks-ipns).\n\n###4. Configure your PayFac settings\nIf BlueSnap has set your account up using the PayFac model, you must ensure that your checkout pages clearly indicate your merchant name, contact information, and the links to your Terms & Conditions, Refund Policy and Privacy Policy.\n\n###5. Comply with PCI requirements\nYou will need to submit your SAQ forms to confirm your adherence with PCI security standards. BlueSnap has partnered with [SecurityMetrics](https://www.securitymetrics.com/) to assist merchants in completing the correct SAQ. \nFor more information, see [PCI compliance](doc:pci-compliance).\n\n##Get paid\n\nWhen you're ready to launch, simply set up your payout method so that you can start getting paid through BlueSnap. For details, see [Payout](http://support.bluesnap.com/docs/payout-method).","excerpt":"Great job! You set up your BlueSnap API integration, and now it is time to get ready for launch.","slug":"prepare-for-launch","type":"basic","title":"Launch & Get Paid"}

Launch & Get Paid

Great job! You set up your BlueSnap API integration, and now it is time to get ready for launch.

Let's walk through some key items you'll want to handle before you launch, so that you can achieve frictionless checkout and maximize your payment conversions. Then you can start getting paid!

Prepare for launch

1. Set up your statement descriptor

The statement descriptor (or "soft" descriptor) is the description that shoppers see on their credit card or bank statement for each transaction. The descriptor typically includes the business name and a shopper support phone number. It can also include information such as the product name.

You should set a default statement descriptor for your account, and you can also define descriptors dynamically per transaction.
See Statement descriptor.

2. Understand your fraud prevention options

BlueSnap partners with Kount to offer three levels of fraud prevention services: Managed, Merchant Configurable, and Enterprise. Every merchant is automatically enrolled in the Managed level of fraud prevention.
Learn more about what this means and whether an enhanced level of fraud prevention may be right for you.

3. Enable real-time event tracking with IPNs

Instant Payment Notifications (also known as Webhooks) send real-time notifications about transaction events directly to your system. These notifications include basic information about the transaction, such as price, product, and shopper information. IPNs are sent in HTTP POST format to a unique URL that you define.
See IPNs (Webhooks).

4. Configure your PayFac settings

If BlueSnap has set your account up using the PayFac model, you must ensure that your checkout pages clearly indicate your merchant name, contact information, and the links to your Terms & Conditions, Refund Policy and Privacy Policy.

5. Comply with PCI requirements

You will need to submit your SAQ forms to confirm your adherence with PCI security standards. BlueSnap has partnered with SecurityMetrics to assist merchants in completing the correct SAQ.
For more information, see PCI compliance.

Get paid

When you're ready to launch, simply set up your payout method so that you can start getting paid through BlueSnap. For details, see Payout.