Secure Java API, when used in conjunction with the Triggered add in, enables you to process transactions through your own web site or other application without the need to be transferred to a SecurePay or third party web site – but it means you can do so in a way that meets PCI DSS security requirements.

Use the SecurePay Merchant Log In to set up your customer with a “Customer Number”. You can set up their credit card, charge card, debit card or debit bank account details. These details are stored by SecurePay within SecurePay Vault, a service fully compliant with PCI DSS security requirements.

You then use the SecurePay Java API to send payment transactions, referenced with the “Customer Number” and not containing any card or bank account details, in order to effect a payment.

SecurePay Vault “looks up” the relevant card or bank account details and effects the payment.

Payments can be uploaded in a batch file via the SecurePay Merchant Log In to effect batch payments for credit cards, charge cards and debit cards.

Payments can be effected one by one via the SecurePay Merchant Log In for credit cards, charge cards, debit cards and for debit bank accounts.

Check out our easy to use Integration Guide: