Mollie split payment after user approval - payment

I have this problem, that I want to solve in Laravel 5 (preferably using Mollie).
My platform offers multiple account (free to create, no professionals)
that offer services at various prices. I want a flow where the
customer pays on forehand, and when both parties (customer and service
provider) arrive on scene, they 'accept' the payment and the money
flows to the service provider.
Let's say I want to use serviceA from accountA (User: Jeff, service: painting). I order Jeff for next monday to paint my room, but I need to pay on forehand to ensure Jeff he is really needed here. To make sure Jeff is actually showing up, I want to 'hold' the money somewhere, that is only released when Jeff is on sight and the customer 'accepts' Jeff's presence. When the customer accepts, 95% goes to Jeff, 5% is kept as fee.
I have contacted Mollie, they told me it is not possible the 'hold/freeze' money in Mollie or in the cloud.. Blablacar (for example) let's users pay to blablacar, and they on their turn pay back the money when the user is delivered (minus a small fee). Only problem I see here is that I want my platform to be stand-alone. When both the customer and the service provider click 'accept' the money transfer should happen automatically. Is that even possible? Payments always required some sort of password or identification.
Is there an obvious other (easy) method I am missing? First time building a platform with payments, so I have no experience with any service whatsoever..
Thanks for your expertise and help.


How to process payments through cards? [closed]

I'm developing a web application, using and C#
need to provide a functionality through which users can pay through their cards (Credit card, Master card, Visa card, Debit card etc.)
how do i process a transaction, means that when user enter payment details and click on pay button,
how do i verify that these payment details are valid and money is transferred to merchant account.
I never handle payments before, so where do i start with?
You need a third party company to process the payments. PayPal is popular, FDMS, or talk to your bank to see what solutions they offer. Usually these come with an API document or some code libraries to help you start.
And be sure to be aware of PCI-DSS security requirements for merchants. They can make your project more complex than you can solve with code. =)
braintree is a popular payment service that handles a lot of this work for you.
Check out their docs, specifically, New to payments and the .NET api.
The most important thing you need to remember is to never store any of their information unless you absolutely need it (pre-orders or something like that). In my work's case, we use a third-party system, Touchnet, to handle all of the credit card processing.
Our custom applications record the amount and a special transaction number in a database before forwarding the user on to the credit card portal. After the user completes the transaction (by cancelling or paying) the third-party contacts our web service with the custom transaction number and the reference number of the payment. At this point our web service finds the transaction in the database and marks it appropriately and sets the reference number if one was provided.
Our finance department takes care of reconciling the transactions and makes sure we get paid. (I've never seen that part so I can't say how it works...)
By using a third-party to process transactions, some of the PCI-DSS compliance is taken care of, and we can truthfully tell our users that we never store their credit card information.
Full disclosure: I work for PayJunction, the company hosting the link I am providing:
At the above link, you will find some C# sample code for doing credit card transactions through PayJunction. We act as a PCI compliance shield (our merchant agreement stipulates that you never store card information and some additional things that place you outside the scope of PCI).
You might also want to take a look at going through PayPal. Even though they charge a heftier fee, people recognize the PayPal brand. PayPal also shields you from PCI compliance.
If you were doing Rails, I would suggest ActiveMerchant (I always suggest ActiveMerchant). They do a good job of abstracting a bunch of gateways. Don't know of an equivalent for C#.
ah, handling credit cards are a pain! Watch out for the PCI requirements when dealing with payments. I used to work for Mercury payment systems. they have a wide range of API's you can integrate to. here is there developer integration page:
good luck!
First thing I recall doing 10 years ago with E-Commerce was building my own shopping cart (Not necessary) Then I researched both GATEWAYS and MERCHANTS. Many times they are separate. For example: Verisign is a GATEWAY , this is important as they are providing YOU with the API that you need to learn and build with. I started out with with my own, and moved onto oscommerce which is free but IMO the PHP code is just awful to work with for manipulation. I use to contribute free things. I used a few gateways and a few merchants with them. Merchants are the banks. Bank of America I'm not a fan of , but they have both a gateway and they are a merchant as they are the end bank. Sometimes a one stop shop is nice. For a ASP.NET/C# solution I'm not recalling any free or open-source ones that I liked. So for .NET, I would purchase one or perhaps your hosting provider has one.

Implement a paid subscription service on a website

I have a website and I would like to implement a paid subscription service. Its a simple service with only 2 types of plans. For now, ill just use Paypal. But im a little lost before start, mainly with the data model.
My main question for now is, what information do I need to keep for each subscription? Do I need to implement a shopping cart for this (dont think so)? Im not asking for a detailed explanation, just a few lights or resources to find a way to start. Thanks.
Look at any subscription card mailer from any magazine and you can get an idea of what kind of data you will have to record. Start and end date for the subscription would be a good thing to keep, and what kind of plan the user is subscribed to. Once you have the end date, you just need to run a query to get the records of the users that have access. Something like
Select * from users where subscription_end_date is >= today
I'm sure there will be a lot of other columns that will go into your final product, but that will be up to you to decide what data you want to keep. What are the different states that a subscription can be in? Can someone be subscribed to both services at the same time?
Depends on what technology you're using. Basic payments work a bit like this
-> You send them to paypal with a plan (you define the plan on paypal)
they know which amount to charge
you can pass custom parameters which they will pass back
Customer fills in application
<- paypal tells you that your predefined plan got purchased
in this same request, they send a lot of info about the payment including a GUID and your params
-> you ask paypal "hey, some one just told me this plan GUID got purchased, can you confirm"
<- paypal service returns 'yes'
-> you take the customer's ID from the params that you attached when you sent them to the paypal service and update them to "paid" in the database, or whatever
That's it in a nutshell...
PayPal does a decent job if you want to charge the same amount every month. However, if you anticipate your users making changes to their subscription plans (upgrades/downgrades) or needing to provide credits to their account for customer support purposes, PayPal would require that you cancel the subscription...and then have the customer re-subscribe.
[Full disclosure - I am a co-founder of]
Recurly handles the upgrades and downgrades, and provides automated customer emails to be sent out to your customers (on your behalf) for every event confirmation, and invoice that occurs. You also have a full account management dashboard and reporting so that you don't need to build this yourself.
Best of all, if you ever decide to leave PayPal, and move your business to a standalone payment gateway, Recurly stores all of your credit cards in a PCI compliant vault so you don't need to ask you customers to come back and re-subscribe. (PayPal will not return your customer credit card information). You simply configure your new gateway in Recurly, and payments will be processed without any interruption to your business.
Here is a blog post we wrote on the topic:
-Best of luck.

Subscription Based Billing [closed]

I'm putting together a small start up company which will be set up with a subscription based billing model. The bill will go to customers on either a monthly or quarterly basis depending on the end user's preference. My question is two parted:
I'm new to online billing and I'm only really aware of Pay Pal when it comes to third party bill payment, but this seems more like a check out system. I'm sure there are better alternatives than PayPal for third party billing processors (I have tried Googling for them, but I'm having trouble finding exactly what I'm looking for). What options (companies) are available for third party payment processing and what types of experiences (good or bad) have you had with them?
We would like to give our customers the ability to set up recurring payments. I'd rather not store a customer's credit card number on our database as I imagine there are a plethora of compliance guidelines around this. Is there a third party solution for recurring payment processing?
On a side note, this is not necessarily a code related question and is more business focused. I wasn't sure if there was a better route for posting this question, and please commont or modify this if there is another route I should take.
You can also look into Amazon Flexible Payment System. I implemented this for a customer and the API, at least, was very easy to work with, and Amazon seems solid and trustworthy as near as I have been able to tell.
Take a look at
There are many business out there that will fit the bill. Be sure to look for a solution that believes in Credit Card Data Portability - which means that they'll transfer your credit card data to another vendor should you want to leave them in the future.
You have many, many options. Take a look at Recurly (where I work), Chargify, Stripe, CheddarGetter,'s ARB, PayPal's recurring billing, Braintree, etc.

How can I electronically transfer money to another account using Bank Transfer (BACS)

I'm working on a project where we collect payments from users using credit/debit/PayPal payments.
The service is taking payments from users on behalf of a 3rd party organisation.
Once we take the payment, minus fees, we want to transfer the amount to the organisations bank account.
For now, what we can do is pay the organisation using Online Banking BACS bank transfer.
But I would like to know if there is a way to do this automatically using an API.
If we need to somehow register the 3rd parties bank account details before making transfers, this is fine.
We just want to automate the whole process, since at the moment the transfer is a manual step.
Are there any gateways or APIs I can use for this? In the UK?
As this is still un-answered I'll throw my hat into the ring.
For the benefit of non-UK users, the UK has a central clearing system called Bacs, which is run by the major banks in the country. However, companies can also makes submissions directly to that clearing system, by using Bacs Software.
There are a number of companies that sell on-premise and online services/APIs that allow you to send money directly via Bacs (and collect Direct Debits).
DISCLAIMER: I currently work for a software company (Bottomline Technologies) which sells a Bacs API - I won't mention the product name and to see alternative companies you can simply Google for 'bacs software api'
Hope this helps
You are going in the wrong direction. You should talk to payment processors (which may or may not include your bank) about the business considerations, which probably are more important than the technological considerations. Generally you can expect something somewhat reasonable that you will (after fiddling with it enough) be able to convince to work. It doesn't matter whether this involves some sort of api library, soap calls, or other communication method.
If you honestly consider having the technological considerations more important than the business considerations, then just go with Paypal and don't write your own shopping cart stuff at all. This is easier to use and will do more of the heavy lifting for you, but which will also probably charge you more.
Once you create a real shopping cart and start handling payments yourself (i.e. taking in CC information and sending it to a payment processor), you start getting into a mess of legal and technical concerns involving PCI compliance and the like, which will apply regardless of your choice of payment processor*.
*This is US-specific, but I bet the UK has something similar.

Canadian website payment processor recommendations? [closed]

This question has been asked before (link) but I have slightly different requirements. First, I'm in Canada so that rules out Google Checkout and probably a few others. I just need a basic service that provides "Buy Now" functionality, no shopping carts or anything like that. The site isn't super high volume, so I'd like to avoid any site with crazy monthly fees. I also need the ability to setup "discount codes" (or whatever you want to call them) for special promotions. The site must also have some sort of payment notification service (IPN). I am currently using PayPal, but their lack of discount codes is really starting to restrict what I can do.
What have you used, or what would you recommend I investigate further?
I have used Beanstream in Canada. They provide a hosted service, where you provide a link to a custom Beanstream page in your site; they do all the payment processing and deposit the funds in your bank account. You can edit the checkout page to make it match your site, and create shopping carts or provide charges on a case-by-case basis. I know you said you don't need a shopping cart, but it is only $10/month more.
They also provide a gateway API if you want to accept credit cards yourself, but I find the hosted service far more convenient.
I've had good luck with eMetrix. Also I've heard good things about Plimus too.
Has anyone had any experience with eSellerate?
Plimus looks good, although I've heard some horror stories from the customers point of view related to their phone verification.
On TeamMentor we use Payflow Pro and have had a good experience with it. The SDK is straightforward and easy to use especially if all you need is a quick "buy now" option. They support international processing, although no paypal processing outside of the US.
I saw the usage of Moneris at a client site.
I have used the Payflow Pro and the Paypal Payments Pro. I found them easy to use from an API standpoint, although Payflow's php API worked well, it required a recompile of php and that meant less ease for patching our servers. After the server setup each was equally okay. The biggest drawback to using the Paypal products was the customer support and set up. Setup was a nightmare and the "salesman"/account rep that we dealt with was less than helpful.
Maybe You should add some details about Your requirements:
If sufficient, try bank transfers. They are not known or free in all countries and I do not know about Canada, but it is the best payment system in Europe: You just tell Your bank to transfer the money to the destination account.
Cannot be undone.
The customer has a proof of the payment.
Free of charge (most banks in Europe)
Cannot be undone ;)
The customer has to order his/her bank to transfer the money.
It takes up to three days before the money appears in Your account.
Do You need "instant" payment?
International payments?