Which are secure ways to get authentication done to an app

Any help with the best way to store your customer login details example Firebase, or host a database like MySQL on digital ocean, use Azure, self-host maybe Rapyd have a built-in system which would be a plus.
I wish to hear as many possible technical solution and inexpensive way to go about keeping clients data secure.
Suggestions are also fine…

1 Like

@Brix, Rapyd, Firebase, Azure are all secured.
In terms of cost reduction, in my own opinion. Firebase will be costly on the long run unless you have other area of your app that requires real-time data integration.

The best bet will be to go with Rapyd and possible with Mysql DB.

You can store Customers login Credentials in Mysql Database while storing other data to Rapyd API. Your backend Programming Language depends on you

For Instance you can create mysql table like

create table Customers(id int primary key auto_increment, customer_name varchar(50), customer_email varchar(50), customer_password varchar(50), customer_identity varchar(50), date_time varchar(50));

Table column customer_identity is what you will use to create and identify your customer with Rapyd Customers Object Creation.

Programatically you will need to send a request to create a customer to Rapyd Customer Creation End Point. here is a sample of successul message response.

    "status": {
        "error_code": "",
        "status": "SUCCESS",
        "message": "",
        "response_code": "",
        "operation_id": "ac7f0144-b3c1-4af1-bd63-2a71d3606395"
    "data": {
        "id": "cus_7ccd7fe7fd771f34faa6bd84d920aec4",
        "delinquent": false,
        "discount": null,
        "name": "John Doe",
        "default_payment_method": "",
        "description": "",
        "email": "johndoe@rapyd.net",
        "phone_number": "+14155559993",
        "invoice_prefix": "JD-",
        "addresses": [],
        "payment_methods": null,
        "subscriptions": null,
        "created_at": 1575472963,
        "metadata": {
            "merchant_defined": true
        "business_vat_id": "123456789",
        "ewallet": "ewallet_ebfe4c4f4d36b076a21369fb0d055f3e"

Once the request is successful, get all the need parameter especially “id”: “cus_7ccd7fe7fd771f34faa6bd84d920aec4”,

and use it to insert into your customer_identity column in the database. Its just very simple.

Here is the Rapdy API for creating Customers Object Docs API

Let me know if you still have issues.

1 Like

Hmmm. “Customer login details”, eh?

Let’s be clear about who is logging in and where. Your customer (the end user) might log in to your website or app or whatever. How you store that data is up to you. @fredjinbility offered some suggestions, so I would start with that.

Your website or app back end needs to use access credentials to send requests to the Rapyd API. It’s not a login process - every request must contain the access key and the signature (among other things). See Message Security and the pages after it.

The customer object on the Rapyd platform is a customer profile that stores information about the customer’s available payment methods. It has nothing to do with access keys or login details.

@CharlesDorsett yes, the customer refers to the end user.

1 Like