Accepting virtual cards with Coupa and Boost enables you to get paid quicker and easier with a fully automated processing solution.
Boost and Coupa are partnering together to launch a mutually beneficial and fully automated virtual card program. Bring your accounts receivable up to speed with the most efficient B2B payment solution available.
Boost handles reconciliation, straight-through processing, and delivers secure virtual card transactions, so suppliers can easily:
Our goal is to ensure your virtual card program is as beneficial as possible. Enjoy the following benefits:
Virtual credit cards are a flexible electronic payment method using 16-digit credit card numbers typically created for purchases at set amounts. Most commonly sent via email, they offer convenience, security, and speed in the B2B payments space. Virtual cards can improve accounts payable (AP) processes, benefitting both buyers and suppliers by streamlining day-to-day payments, and providing greater control over cash flows. They also offer more safeguards against fraud than traditional business credit cards.
Boost processes virtual cards in an automated way, eliminating manual processing steps.
Getting started is easy. If you are already a Boost customer, just email us at inquiries@boostb2b.com or contact us using the form on this page and let us know the customer that you want to accept payments from via your Boost account. We’ll then verify and confirm your account information, and begin automating your payments. No further action is needed on your part.
Boost provides enhanced reporting with full remittance and settlement details. Reports are available in a CSV format or in the format of your accounting software and can be selected with the help of our customer service team after enrollment.
Boost offers the lowest possible business to business card acceptance fees. Boost’s rates are available here.
Yes. Boost suppliers are never exposed to 16-digit card numbers. All live card data is encrypted and tokenized and the supplier (and Boost) are never exposed to it. Only the last four digits of the card numbers are shared with the supplier for tracking purposes. Consequently, as card data is not shared with the supplier, the supplier is not beholden to PCI compliance requirements for the payments that Boost processes.
No, the funding process is completely automatic, and the transactions will qualify at the lowest published B2B interchange rates. Virtual cards from your customers are automatically processed by Boost and the funds are deposited directly into your preferred bank account by Boost.
Transactions through Boost will not be delayed, regardless of transaction size. Boost processes multi-million dollar card payments almost every day. Boost processes the virtual card payments for Fortune 100 companies and thousands of smaller companies, too.
From the time when your customer sends the virtual card for payment, the funds will typically be in your bank account within 24 – 72 business hours depending upon the bank-to-bank relationships between Boost’s funding bank and your bank.
Once the application is completed, it will take five to seven business days for account set up. The Boost customer service group would typically reach out if there are any questions about the information provided or if any required information is missing.
No, these payments would be processed by Boost and there will be no fees from any other processor that you use. You would not be paying two sets of card fees.
There are no monthly or other charges beyond the per-transaction fees. If there are no payments processed by Boost in a given month, there will be no charges from Boost for that month. There is no long-term commitment to use Boost – you can use your Boost account when you want and you are free to switch processors at any time.
Boost will need either a voided check or a bank letter on bank letterhead that provides the bank account details for funding so we can deposit the funds into your preferred bank account. We cannot accept banking information on the company’s own letterhead. This is required to meet Anti-Money Laundering (AML)/ Know Your Customer (KYC)/ Financial Crimes Reporting Network (FINCEN) regulations. The voided check or bank information on bank letterhead should be scanned and saved as a PDF file and emailed to registration@boostb2b.com.
Publicly traded companies are not required to provide beneficial ownership information, but the ticker symbol for the company must be provided. Most companies are privately held (meaning they are not listed on a major stock exchange) and will need to complete some additional fields in the Boost application including providing a social security number, birth date and an address (as provided on a driver’s license) for a beneficial owner or control manager. Boost Payment Solutions partners with regulated financial services institutions and, as such, we are required to obtain this information from all privately held companies to comply with Anti-Money Laundering (AML)/ Know Your Customer (KYC)/ Financial Crimes Reporting requirements via the Bank Secrecy Act, USA Patriot Act, and Financial Crimes Enforcement Network (FINCEN) regulations. To confirm, this information is not used for any purpose by Boost other than to meet federal regulations. These regulations apply to the set up of all merchant processing accounts and any new merchant processing or bank account will require the same information to be provided. In fact, any company that has opened any merchant processing or bank account since May 11, 2018 would have been required to provide this information.
Most companies elect to provide the information required from a “control manager” rather than a beneficial owner, which is sometimes difficult to capture. A control manager can be a manager in the company’s accounting or finance group.
Here are a few links that explain why Boost is required to obtain this information:
https://www.fincen.gov/news/news-releases/fincen-reminds-financial-institutions-cdd-rule-becomes-effective-today
https://www.fincen.gov/sites/default/files/2018-04/FinCEN_Guidance_CDD_FAQ_FINAL_508_2.pdf
Boost maintains strict protocols for information and data security as well as confidentiality and privacy. As noted above, we are subject to FINCEN (Financial Crimes Enforcement Network) and Anti-Money Laundering rules and are required to maintain specific PII (Personal Identifiable Information) as per government mandate.
We hope you understand our requirement to gather this information and will complete the fields in the application so we can complete the setup of your Boost account.
Cookie | Duration | Description |
---|---|---|
__cfruid | session | Cloudflare sets this cookie to identify trusted web traffic. |
ASP.NET_SessionId | session | Issued by Microsoft's ASP.NET Application, this cookie stores session data during a user's website visit. |
CookieLawInfoConsent | 1 year | CookieYes sets this cookie to record the default button state of the corresponding category and the status of CCPA. It works only in coordination with the primary cookie. |
OptanonConsent | 1 year | OneTrust sets this cookie to store details about the site's cookie category and check whether visitors have given or withdrawn consent from the use of each category. |
viewed_cookie_policy | 1 year | The GDPR Cookie Consent plugin sets the cookie to store whether or not the user has consented to use cookies. It does not store any personal data. |
Cookie | Duration | Description |
---|---|---|
m | 1 year 1 month 4 days | No description available. |
visitor_id492571 | 1 year 1 month 4 days | Description is currently not available. |
visitor_id492571-hash | 1 year 1 month 4 days | Description is currently not available. |
Cookie | Duration | Description |
---|---|---|
bcookie | 1 year | LinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser IDs. |
bscookie | 1 year | LinkedIn sets this cookie to store performed actions on the website. |
li_sugr | 3 months | LinkedIn sets this cookie to collect user behaviour data to optimise the website and make advertisements on the website more relevant. |
lidc | 1 day | LinkedIn sets the lidc cookie to facilitate data center selection. |
UserMatchHistory | 1 month | LinkedIn sets this cookie for LinkedIn Ads ID syncing. |
VISITOR_INFO1_LIVE | 5 months 27 days | YouTube sets this cookie to measure bandwidth, determining whether the user gets the new or old player interface. |
YSC | session | Youtube sets this cookie to track the views of embedded videos on Youtube pages. |
yt-remote-connected-devices | never | YouTube sets this cookie to store the user's video preferences using embedded YouTube videos. |
yt-remote-device-id | never | YouTube sets this cookie to store the user's video preferences using embedded YouTube videos. |
Cookie | Duration | Description |
---|---|---|
_ga | 1 year 1 month 4 days | Google Analytics sets this cookie to calculate visitor, session and campaign data and track site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognise unique visitors. |
_ga_* | 1 year 1 month 4 days | Google Analytics sets this cookie to store and count page views. |
ai_session | 30 minutes | This is a unique anonymous session identifier cookie set by Microsoft Application Insights software to gather statistical usage and telemetry data for apps built on the Azure cloud platform. |
ai_user | 1 year | Microsoft Azure sets this cookie as a unique user identifier cookie, enabling counting of the number of users accessing the application over time. |
AnalyticsSyncHistory | 1 month | Linkedin set this cookie to store information about the time a sync took place with the lms_analytics cookie. |
CONSENT | 2 years | YouTube sets this cookie via embedded YouTube videos and registers anonymous statistical data. |
ln_or | 1 day | Linkedin sets this cookie to registers statistical data on users' behaviour on the website for internal analytics. |
pardot | past | The pardot cookie is set while the visitor is logged in as a Pardot user. The cookie indicates an active session and is not used for tracking. |
Cookie | Duration | Description |
---|---|---|
__cf_bm | 30 minutes | Cloudflare set the cookie to support Cloudflare Bot Management. |
elementor | never | The website's WordPress theme uses this cookie. It allows the website owner to implement or change the website's content in real-time. |
li_gc | 5 months 27 days | Linkedin set this cookie for storing visitor's consent regarding using cookies for non-essential purposes. |
Cookie | Duration | Description |
---|---|---|
_calendly_session | 21 days | Calendly, a Meeting Schedulers, sets this cookie to allow the meeting scheduler to function within the website and to add events into the visitor’s calendar. |