Brick is a convenient way to accept payments online, charge credit and debit cards on your website or in-app.
Brick gives you a merchant account to handle credit card processing. Choose your preferred API and start accepting payments from all over the world.
Brick has your back. Contact our support team at firstname.lastname@example.org so we can assist you.
Brick is an innovative credit card processor that allows online businesses to accept credit card payments in a quick, simple, and easy way. We deal with the payments angle, for you to focus on your business' growth.
Brick processes payments from over 180 countries, excluding those under U.S. Department Of The Treasury sanctions, such as Syria, North Korea, Iran, Sudan, and Burma.
Brick is available for businesses from 29 countries:
United States, Austria, Belgium, Bulgaria, Croatia, Republic of Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, United Kingdom.
Brick processes payments in more than 75 currencies, including USD, EUR, GBP, RUB, JPY, CHF, CND, CNY, BRL.
Yes. Android SDK and iOS SDK are available for use.
Implement Brick Checkout (Retrieving Credit Card Information)
The purpose of the checkout is for you to get your customer's credit card details, which would then be passed to the backend for processing.
Integrate Brick API (Charging the Credit Card)
The backend script functions as a billing service for the token retrieved by the frontend script.
Testing and setting up a pingback
For testing purposes (to check if forms for getting credit card information are working, and/or if a credit card is to be charged), your merchant area allows you to use these API keys:
Details on the test CVV/CSC values are found on the Documentation page.
From the home page of your merchant account, click on My Projects tab located on the left side of the screen.
On the same project, click on Brick Live Keys and click GET LIVE KEYS, the green button below.
A pop up page appears. Click on PROVIDE YOUR PAYOUT DETAILS AND DOCUMENTS.
On the Payout and Compliance tab, please provide all your documents in order for us to speed up your application approval.
Before you receive the Brick Live Keys, you have to submit the necessary Compliance documents.
Yes, Brick has plugins for several shopping carts and we continuously add more, including:
If you do not see a plugin that you use on our list, please email us at email@example.com so we can add your preferred shopping cart plugin.
When a user makes a payment, we send you an HTTP/HTTPS server-to-server notification communicating their user id and the details of the purchase. We call this notification a pingback.
You can refer to the documentation page for instructions on how to set up a pingback. Upon receiving a pingback and processing the order on your side, we also recommend implementing the Delivery Confirmation API so Brick can track the order status (in case of non-instant delivery) and update users if they inquire about the payment status. Brick can then dispute possible chargebacks.
You can set up custom pingback parameters in My Projects > Settings > Custom Pingback Parameters section. Any custom parameters can be added by specifying their name and value. For elaborate instructions, check out the pingback parameters page.
HTTP request is sent from our servers to your Pingback listener script where we communicate to the details about the payment to your server so it can process the pingback and deliver the product or virtual currency to the according user automatically.
With Email Pingback, an email is sent to the address that you configure once a user pays or completes an offer. Once you receive the email, you should deliver the product manually to the user.
We highly recommend using HTTP Pingback for an automatic processing of orders.
If there is any third-party provider (e.g. Cloudflare) that routes the traffic to you and your pingback script stopped working, the IP whitelist check in your pingback script may be the reason. In order to resolve this you can do one of the following:
Check the request headers and server variables to see if the original IP of the request is present in another variable or header (e.g. X-Real-IP header). If so, use this variable for IP whitelist checks.
Add IPs of the third party provider into whitelist of IP addresses in pingback script. (not recommended) Remove IP whitelist check from pingback script. Pingback signature check still needs be in place.
Please add the following IP Addresses as authorized IP addresses to access the script:
Brick Checkout is a multi-platform payment form that can be embedded on a site or app for one-click payments.
Yes. The checkout form can also be integrated in small, transparent iframes.
Yes. Brick allows you set up due dates to automatically charge subscribers.
There are no setup fees or monthly fees in order to use the recurring billing feature of Brick. Charges only apply per transaction.
Recurring billing can be activated in the Merchant Area. Go to Analytics, then enter details for recurring billing in Subscriptions.
Brick will make two more attempts to charge the customer. Brick will stop the recurring billing if all attempts fail.
Yes. Please refer to Marketing Tools found in the Merchant Area.
Brick is PCI DSS Level 1 Compliant, the highest level for online credit card security standards.
PCI DSS (Payment Card Industry Data Security Standard) is a set of protocols to develop, protect, and implement proper handling of debit and credit card transactions. More information on PCI DSS standards can be found here. .
Yes. You are required to be PCI DSS compliant if your business needs to accept credit card payments. Brick requires businesses to fill out and submit a PCI DSS SAQ A (Self-Assessment Questionnaire A) form during merchant account verification. Compliance with PCI DSS regulations means that transactions done on your site are secure, and that your business is a safe and trusted site for customers and financial institutions to work with.
The table below shows PCI DSS requirements for each integration type.
|Integration Type||SAQ Type|
|Widget integration (iframe)||SAQ-A|
|Direct API / Server-to-server||SAQ-D|
Your ability to accept credit and debit card payments will be suspended.
You can always reach us at firstname.lastname@example.org to get assistance from our team.
We don't charge any monthly or setup fees. We take a revenue share from the volume of transactions you process. This means that we won’t charge you anything if you did not have any payments.
United States: 2.7% + $.30
European Union: 2.7% + €.30
Volume pricing is available for businesses who process more than $100,000 per month.
Transaction details can be found in the Analytics tab in your Merchant Area. You can generate a transaction report by entering the User ID or Reference ID.
A cross-border fee is a charge applied by VISA and Mastercard for transactions that require currency conversions. This occurs when a transaction is made between two countries, where a buyer uses a different currency to make a purchase. Read more about cross-border fee on VISA or Mastercard website.
We can pay you via the following methods:
The payout can be put on hold for a prescriptive period of time (no less than one month) if we see that you have stopped processing payments. This is to cover any possible chargebacks the users may file. Once the prescriptive period is over, we pay the remaining balance back to you, excluding any refunds or chargebacks that might occur during the prescriptive period.
We can send the payout in USD or EUR, depending on the currency denominated by the bank used for the deposit.
You receive payouts once a month. We can only send payouts twice a month if your monthly revenues are greater than $100,000.
If you are a minor and would like to use our service, kindly ask your parents or legal guardians to accept the payout on your behalf. In compliance with international laws, we require the beneficiary of the payout to be of legal age.
There is a $100 minimum payout threshold. Once the $100 threshold is met, we will automatically send you the payout as long as all compliance documents are submitted and approved.
Go to Research and Refund in your Merchant Area. You can add refund ticket by selecting transaction for refund by entering User ID or Reference ID.
The in-house developed risk scoring system can put on hold customer's charge if fraud is suspected. Brick’s risk monitoring team will review it and make a decision to decline or accept suspected charge.
Please pass as much User Profile API information as possible along with every Charge or Subscription API creation request. This is to ensure that Brick's team of risk analysts and in-house risk scoring system have all the necessary data to score transactions accurately.
A chargeback is when a customer contacts their own bank and demands for a refund stating the charge is fraudulent. If it happens, the transaction is refunded to the customer and the merchant is charged a fee by the card issuing bank.
There is a minimum and fixed chargeback fee of $15 USD.
You can prevent them by implementing a User Profile API to ensure that Brick's team of risk analysts and in-house risk scoring system have all the necessary data to score transactions accurately.
Yes. Please send us an email at email@example.com and we’ll help you win chargeback disputes.