 And what I'm going to be talking about today is something I guess quite specific. I don't have any slides or anything, so I'm just going to quickly walk through some of the things that you might be interested in if you are looking to accept payments within an application. Now, I know I've already talked to a few of you who are interested to know. And if I'm not clear throughout the session, feel free to just catch me as well. I'll be here the rest of the night. So how many of you have heard of brain tree? So for those who haven't, it's essentially a startup that's headquartered in Chicago. And it's a payments platform that enables developers to easily accept payments within their apps, so either web apps or mobile applications. And then it was acquired by PayPal about one and a half years ago. And now it's available in this part of the world as well, in the three countries, Hong Kong, Singapore, and Malaysia. So if you're a merchant that is looking to accept payments and you're based in one of these three countries, then you'll be able to use brain tree. As a customer, you'll be able to pay from anywhere. So those countries are only restricted to where the merchant is based and where they have their bank accounts, basically. So the way it works, really quickly going into the technical details, it's actually really simple. So there's only three to four basic steps that you have to do in order to start accepting payments within your application. So for every application that wants to use brain tree, you'll need to have both the client side and server side. Now, client side is obviously your iOS app. And then the server side, it's pretty much available in any server language that's available today, like JavaScript, Ruby, Python. We have SDKs for each of those server languages. And when your application first starts, all it needs to do is request for a token from your server. And there is a server SDK function that just basically generates a token and you pass it back to your application. And with a token, you can then set up your application. And this basically tells brain tree to associate your application with your brain tree account. And once you have that set up, the client side SDK, the cool thing about the client side SDK is that the whole interface for developing a credit card form, for example, is already provided to you. So you don't actually have to go through all the, building the UI yourself, like putting in the text fields, putting in the credit card validations. Everything's all provided for you. And you just need to call the form when you're ready to accept money. And once your form shows up, the user goes in, they can log in to pay through PayPal, they can just log, they can just put in their credit card numbers. And once they click pay, everything is all done by the SDK. It tokenizes all that credit card data into what we call a nonce. And this nonce is important because as a merchant, you don't want to be handling any of that sensitive credit card details because there are compliancy issues that you have to, you know, you have to be PCI compliant basically to be able to handle all that sensitive data. But with the solution here to tokenize that credit card information, you're not actually touching the credit card details. So that liability is on us who are the SDK providers and not you. So you don't have to go through the trouble to be PCI compliant. So once you have the nonce, you call a server side SDK function to say, I want to charge this nonce or which is basically this payment method, X amount of dollars, $10, $20, whatever you'd like, and bring sure we'll do all that transaction for you. So I'll charge it from the credit card and then within three business days, it'll be settled into your bank account as well. So let me just quickly show you a demo of how this looks like. What I have here on the client side, I have my very, very, very basic iOS app. And on the server side, I'm using a node. I'm writing a node. So I have a JavaScript. Let's see where it is. Yeah. So this is basically my, this is the core file basically. So it is, let me try to make the font bigger. So these are basically the keys that you get from your control panel once you have a brain tree account. So if I log in here and I go to account user, then we go authorizations. And depending on what server side language you're using, you can just select it right here. I'm using node and just copy. And this is basically my credentials. So I just need to paste it in here. So remember I was talking about how you need, your server basically needs to provide two functions. One is to serve the client token to your client, to your iOS app. And the other one is to take a payment method nonce and then use brain tree to charge that payment method. So the first route I have here is just to get token. And once the request comes in, I'm just using the brain tree SDK, which is the gateway I've declared here. And to generate a client token and then send it back as a response. So it's really dead simple. And then on the client side here, you'll see that I only have one view controller here. So when my view controller loads, let me increase the font here, I'm currently using, there's a, you just basically use a Cocoa Pots. We also have Carther support as well. But I'm using Cocoa Pots here to install brain tree and I'm using a Lomo Fire to make the request. And you basically just create your client. And then as you can see here when my view controller starts, the only button I have is the pay button. And I'm here, I'm disabling the pay button here because I don't want the user to be able to click on it before the application is able to authorize itself against brain tree. So you want to, as a best practice, you want to enable it only after you've set up everything correctly or else things can go wrong. So I'm just making a request to my local server to get the token. And then the response comes in as a client token. And I set up the client, the brain tree client, and then just initialize it with a client token. So at this point, the iOS client knows that this application corresponds to my brain tree account because I have those credentials in there as well. So the exciting part here is when the user presses the pay button, and as you can see, I only have one view controller here and I don't need a separate interface for my credit card form. And that's really the beauty of it. So all I need to do is just create a, what we call a drop in view controller. And it's from the client SDK and it basically just embeds itself into your current UI. So you can declare it as a view controller and then push it onto your UI stack. So right here, it's a navigation controller. So I'm just creating the drop in controller, setting the delegate to myself so I can get the callbacks. And I am just presenting the UI controller and that's all. So as part of the delegate protocol, I am just implementing two functions. One is when the user goes through the whole flow and then I get the non-spec, so the payment was successful. And the other one is if the user cancels the payment. So simply enough, if the user cancels it, I just dismiss the controller and go back to my application. And if it succeeds, the SDK will pass me back a nonce, which is that strain that represent the payment method. And I just post it to my server and the server will take that strain and create a transaction against it, a charge against it. And I dismiss the controller. So let's quickly see this in action here. So I'm just gonna run my server here and my iOS app. So it's just to let me pay button. So at this point, because it's already enabled, so I've already gone through the getting the token and I can check in the log as well. So I've already sent the token on the server side. And then if I just click pay, you see that controller that just popped up? It's actually from the client SDK. I didn't have to create any of this. And the drop-in UI has all the credit card validations as well, and the credit card type detection. So I don't actually, as a user, you don't have to select what payment method you're using, what credit card you're using. It's auto-detecting. So if it starts with three seven, it's American Express or 401 as a visa. And if the credit card number is invalid, it does inline validation as well. So let's the user know right away. So everything is, it comes for free basically. And then the expiration date, I'm just using a fake CVV. And if I just click pay here, you'll see that the transaction is actually created. So I've already gotten the nonce and passed it to my server. And the server here, I'll just show you the code. Just takes the nonce right here and then charges it $4 and then prints the result. Now the result is this, and it's basically like a receipt. So it gives you all the information about the transaction details. So it's been authorized, it's been charged $4. And then you have the option to also pass information like the customer ID so that you can save the payment methods that they've used. And the next time they come back, it's already been set up. If you use apps like Uber, Uber uses brain tree. So once you have your credit card added on there, you don't need to go back to it again. So it's really, really convenient for the users. And transaction comes through and then I can immediately go to my dashboard and you can verify that the transaction has come in. So I've done a few tests today. So that's how much you get directly. Now this is just being authorized. The transaction takes about, it's about within three business days is when it goes into your bank account. So when it gets settled and then deposit into your bank account that you've got linked to the brain tree account. Now in addition to just simple transactions we also support subscriptions as well. So if you want to charge the user on a recurring basis, weekly, monthly, yearly for example, you can do discount plans as well. All the calculation is done on the brain tree side so you don't have to write logic. Save a user switches their billing, they switched their tier plan, the grade level, midway, brain tree will do all the pro rating for you and handle everything for you. And then if you have expiring cards as well, brain tree will actually know because we actually work with a lot of the banks in the region as well. So if a card is about to expire, you actually get a notification so that you can prompt your user to update their card information. And this is essentially it. So if you want to get started, simply just go to braintreedevelopers.com. You can sign up for a sandbox account which is free and you get approved immediately so you can have access to all the APIs that I'm showing you today. And we have a very easy getting started guide so it's basically four steps. Well, two steps, set up your client, which I just showed you on the iOS or if you're writing a different app, mobile app or a web app, you can do that as well. And then on the server side, you select your language that you're working with and we have all the code samples that you can just easily copy and paste and actually test it out before you actually integrate or before you go live with your brain tree account. And when you are ready and you're ready to go live, you just need to send us, drop us an email and let us know and we'll convert your sandbox account into a production account and you can start using the service. And that is basically all I have. If you have any questions, feel free to ask now or I'll be here the rest of the night as well if you want to go in more detail. But this was more of like an overview for all of you. Yeah. Just wondering when will the marketplace feature be available? Yeah, so for those who are not familiar, marketplace is basically a model where you can pay out your customers. If you're, say you're building a platform like Uber or Airbnb and your users, you basically have two sets of users, you have the users and service providers who are exchange services and you're just like a middle man. And marketplace is an API that allows you to do things like this where you can take a transaction from a user like say for Airbnb they take $100 for the rental and you take a service fee and you pass the rest to a sub-account, what we call a submersion which is all your service providers. Now this marketplace feature is available in the US but not yet anywhere else. We don't have a timeline yet on when it's available but the solution we sort of recommend to developers or merchants who want to use this type of feature is to accept payments using Braintree and you can use PayPal mass APIs where you can just automate dispersing your funds to a PayPal account. Now that puts a requirement for your submersions to have a PayPal account so you can disperse funds through that but that's really the best way you can go about it if you don't want to do it manually which is like transferring money to your service providers. So we don't have a timeline yet going back to your question for this part of the world but we are definitely working on that. And in US how you maintain the charge back? Yeah so. Especially for the marketplace because if you have a charge back then automatically you have to take back also the money from the telecom. Yeah so on a simple case it's actually very similar marketplace or simple payments the charge back is of course initiated by the user so if the user is not if anyone's not familiar with the term if say you're selling something to a user and the user finds that the product is broken and they want to refund so that's when the charge back comes back where you're notified by Braintree that you have accepted money where the customer has gone for a refund. So you have the option to fight for the case if you can provide evidence or documentation in saying that you did provide the product and it was in good condition, blah blah blah and Braintree will be actually the one who would investigate on the case to have the ultimate decision to see who wins. So it's basically the user raising the case and then you trying to provide documentation on your behalf to see. The problem is that if you don't have an API in place you have the situation that you may lose your charge back and you cannot, you cover the money from the paper because you have done a mass payment and you have a problem on how to go and get the money back. Also so marketplace has that already in there but in this part of the world yes so it's basically it's like it's a two-way problem because you're basically separating this whole feature into two processes and if the charge back happens on the PayPal side then you're gonna have to work with the vendor alone to get the money back. At this point, yeah, like that's really the best you could do. So yeah, like going back to you, marketplace would raise this new obstacle here as well. Yes. Is there a feature in the Singapore complex to remember the credit card that is already in with the user? Yeah, yeah. So it's not based on Singapore, like it's a feature that's available worldwide. So in addition to just storing credit cards, so all the credit cards are stored on the Brainscreen Vault and whenever you need a payment method you come and tell us for which customer you need it and then we will provide you with the nonce again and you can use that nonce to create another charge. For this to work you'll have to use, you can actually store customer information in our database as well. So when you're creating a new payment method you just assign it an ID. So you have a customer ID like one, two, three and you want to assign the nonce to it. The next time you see that the customer is returning, obviously the ID is tied to your own account management system as well. If when the user comes back and you know that the customer ID is one, two, three you just come to us and you say you want to retrieve payment methods for this customer ID and we'll give you all the payment methods that have been set up by the user and then you can select which one to charge or you can even display it to the user and let them select which, if they have more than one payment method set up which credit card or which PayPal account to use. And in terms of payment methods we, what we're trying to do is we're trying to be like a one stop shop for all different payment methods that are out there. So currently we, in this region here we support PayPal credit cards. In US we support Apple Pay, Android Pay and Venmo as well. And so all the integration is already done on the back end and once Apple Pay or Android Pay makes the way across to Asia as a merchant if you're already on board with Braintree you simply go to our dashboard and you can select what payment methods to enable. So here you can see that I can say disable Venmo or enable Venmo or enable Apple Pay and you just need to set up your Apple ID credentials and without even any changes on the UI side of things without any code changes on the client side that drop in that you saw there will be an additional button that says you can log in with Apple Pay with Venmo. So, but right now in Singapore the only options are PayPal and credit cards. Credit cards, it's the Visa, A-Max Mastercard. Mastercard. Yes, so this is based on transaction. So it's a very, very simple business model. So per transaction in Singapore it's 3.4% plus 50 cents as GD. It's different across regions. So the best way to check is just through our website but the price is also volume based. So if you have a large amount of transactions then the price would obviously be lower as well. And this is something that you would, when you're onboarding with us you would discuss with the team because it's different depending on the nature of your business because it's also based on like other factors like risk and transaction volume and the actual nature of the business like what kind of business are you doing as well. So, but the pricing that we have on the website is basically like the ballpark baseline kind of thing. Yes. Is it possible to do partial re-investment so to speak, right? You can do, so you can do partial capturing. So when a credit card charge happens if you've been to hotels they always ask you to authorize, right? Your credit card for like $500 and if something happens they can capture the money. So that's the two step process like the authorization capture and you can do that with branch fee as well. So you can authorize an X amount of dollars within for a particular payment method and you can capture amounts as many times as you want. So you don't have to do it all at once. You can do, it's kind of like a credit kind of credit-based system. So you can take, you can capture amounts from that $500 anytime you'd like. Yeah. So is the 3.5 based on the two transactions? Yes, it's based on transactions. So everything is based on transactions. So if you split that $500 into like $1 transactions then it would be quite costly. Cool. So again, I'll be here for the rest of the day. So if you feel free to come and just chat with me if you'd like. And I think I'll pass it on to Justin now.