FAQ's

Platform security FAQ's

What security standards is Banking.live certified for?

Banking.Live is PCI-DSS and ISO 27001 certified.

What security measures does Banking.live have in place?

You can view a list of Banking.Live's security measures on the Platform security guide.

Do you have measure in place to stop BIN attacks?

Yes, Banking.Live has security measures in place to protect your card program form BIN attacks.

API security FAQ's

What security measures do you have in place for your APIs?

You can view a list of our API security measures on the API security guides.

Is X-API-KEY applicable to all API's, including PaySecure API?

X-API-KEY is applicable to ALL API endpoints. This includes PaySecure API endpoints.

Does X-API-KEY have a minimum and maximum length?

Maximum length is 32

Can X-API-KEY have special characters?

Yes X-API-KEY can have special characters.

There are no restricted characters.

Transaction security FAQ's

How can Paymentology help protect transactions and reduce the risk of fraud?

Paymentology helps protect your transactions and reduce your risk of fraud in multiple ways. These are all documented on the Transaction security guides.

Where can I find more information about EMV?

You can find more information about EMVCo technologies here.

What security measures do you have in place for transactions?

You can view a list and read more on this in our Transaction security guides.

Is there a rules engine with card fraud functionality?

Banking.Live's rules engine can assist with multiple fraud rules to help you mitigate fraud and manage your fraud risk. You can read more on this functionality in our Additional fraud prevention guides.

If you are considering using our rules engine, you can discuss this further with your Client Executive.