Oh yes, IBM has done it. While I can't recall the name, there was a hedge fund that based its entire trading philosophy on the basis of Twitter sentiment of underlying securities.
06 Jul 2012 11:54 Read comment
This payment method not only bypasses banking rails but also seems to disintermediate Boku, Zong and other providers of GenY / MNO-Billing Mobile Payments. It would be interesting to watch how many other MNOs spurn Boku, Zong, et al, and follow in Telefonica's footsteps.
06 Jul 2012 11:33 Read comment
Sorry Nationwide, a 26% week-on-week rise in account openings by itself doesn't prove that "Customers are clearly unhappy with recent events and are opting to vote with their feet." Tens of millions of people have been affected by the events at RBS, NatWest and Barclays. Only if Nationwide's account openings last week and this week are of similar order of magnitude does it follow that many people outraged by their existing banks really switched to Nationwide from last week to this week. In the absence of absolute figures for account openings, a 26% week-on-week rise really doesn't mean much.
05 Jul 2012 12:22 Read comment
Decoupled debit pioneer Tempo Payments shut down a year or two ago following a losing battle to enter the mainstream. Google Wallet and other mobile payments are struggling to gain mainstream adoption. When you combine the two, you surely get a patent but only time will tell whether commercial success will follow.
03 Jul 2012 16:15 Read comment
With products like iPod, iPhone and iOS Passbook app, Apple has proved time and again that it can disrupt the status quo by taking UX to the next level. While SRI is not Apple, it does power Apple Siri. It'd be interesting to watch if Siri++ Lola manages to do a similar thing to the Jenns, Asks, Shaks and Jos deployed as virtual assistants by Alaska Airlines, Yorkshire Business Society and Milton Keyes Council among other websites.
30 Jun 2012 17:15 Read comment
@KeithA:
Thanks. It's clear that, even under steady state, narrations used by payers is the sole method by which you / a "merchant" can reconcile receipts. That highlights one of the fundamental hurdles to mainstream adoption of ePayments and reinforces my personal view that cheques won't go away in a hurry: While you can impress upon your customers to use full narrations like the ones you've indicated, what happens if some of their banks don't support long enough field lengths for them to be able to do so? I faced exactly this problem when my HSBC UK ePayment form didn't allow me to enter the full narration required by my building management company for rent payment. It was 4-5 years ago but I remember that I had to enter something like "MCS MERIDIAN CLIENT ACCOUNT A62" but all the form allowed me was "MCS MER CLT AC". With such a cryptic reference, I feared that I'd have to spend a lot of time proving to the company that I'd made the payment. As a result, I actually gave up on ePayments in that instance and started using cheques - on the back of which I could write lot more than the minimum transaction details required by the company.
29 Jun 2012 19:11 Read comment
Thank you for explaining. I was previously under the impression that RBS, by itself, was somehow able to convey to you the payer's name (which seems possible although most banks don't do it) and your invoice # (which did appear a bit magical!). I now understand that, at 'steady state', RBS was merely faithfully conveying to you what each payor had entered in the reference field of their respective e-payment instructions. And, in the present turbulent phase, RBS is not even doing that, and is instead substituting individual payor-entered narrations with a standard wildcard. That's surely a disaster! Best wishes with your reconciliation! One question: Under steady state, if a certain payor(s) had failed to enter any Personally Identifiable Information in their reference field(s), how were you reconciling their receipt(s)?
29 Jun 2012 17:29 Read comment
Am I right in concluding that, when all was well, you were actually able to make out your customer's name and your invoice number for all electronic receipts? I've never managed this with any of my banks and I've heard several companies complain that remittance information supplied by most banks is too meager to satisfy the needs of their AR recon systems / people. It may not be the best of times to say this, but it does appears that, until it was hit by its present crisis a week ago, RBS was doing better than many other banks in this department. I'm a bit curious to know what narration RBS uses normally - obviously something other than the wildcard “RBS TRANS 220612” - that delivers such rich information. You can take your time replying in case you're busy sorting out your "here and now" recon problems.
29 Jun 2012 13:27 Read comment
Agreed - I know one bank in the UK which did the "mother of all business transformations" in the case of SEPA Direct Debit: Retire all internal systems and outsource processing to one of its major competitors!
28 Jun 2012 14:23 Read comment
Even if IT budgets of traditional Tier-1 banks get slashed by 10-20% in these tough times, they'll still have many hundreds of millions to spend. So, they're a far cry from startups, most of whom have to manage with a few millions or even less. Besides, there's enough evidence to support the claim that, when traditional banks implement technology right, they can gain massive business benefits. This is unlike startups where only 2 out of 10 are truly innovative / successful. Therefore, MVP / Lean are almost indispensable for startups whereas tried-and-tested methodologies that are fully compatible with their organizational DNA make more sense for traditional banks.
28 Jun 2012 14:16 Read comment
Manoj KheerbatFounder and CEO at Gropay
Guillaume PousazFounder and CEO at Checkout.com
Gilbert VerdianFounder and CEO at Quant
Tamas KadarFounder and CEO at SEON
Olivier NovasqueFounder and CEO at Sidetrade
Welcome to Finextra. We use cookies to help us to deliver our services. You may change your preferences at our Cookie Centre.
Please read our Privacy Policy.