Authorize.net ProPay is a gateway that allows you to collect card payments. This guide is intended to help you implement ProPay based on your preferred integration workflow.

Services and compatibility


Supported payment types	Card
Supported transaction types	Sale (saved card token) ( API / API with iframe / Tutorial ) Auth Only (saved card token) ( API / Tutorial ) Capture (partial or full) ( API / Dashboard ) Void ( API / Dashboard ) Refund (partial and multiple) ( API / Dashboard )
Supported processing currencies	CAD, JPY
3D Secure 1.x supported	No
3D Secure 2.x supported	No
External 3D Secure supported	No
Installments supported	No

Gateway-specific information

Propay does not support capturing more than the amount from the auth only transaction.

Configuration

Work with Integrations Support to add ProPay as a connection. You will need the following credentials from ProPay:

Cert String
Term Id
Account Number

Required fields

The following fields are required when processing a payment request with ProPay:

data.amount
data.currency
processingOptions.paymentType

If you are having issues with transactions that are rejected by ProPay because of potential fraud, include the clientIp parameter in the payment request and explicitly set the value as the IP address of the device where the customer is submitting the payment information. If you do not explicitly set a value, it looks to ProPay as if the exact same IP address is sending out an inordinate amount of traffic and it is not possible to separate out the valid and invalid requests.

Testing data

Use the following test card information to test your ProPay configuration.

Brand	Card number	Expiration date	Security code	Cardholder name	Postal code	Transaction result
Visa	4747474747474747	Any future	999	Any	Any	Success
Mastercard	5454545454545454	Any future	999	Any	Any	Success
Amex	371449635398431	Any future	3714	Any	Any	Success
Discover	6011000000000012	Any future	999	Any	Any	Success
Visa	4616161616161616	Any future	999	Any	Any	Fail

To test specific failures, use the following transaction amounts in conjunction with the card information above that normally would produce a successful transaction:

Amount	Transaction result
1.10	Invalid card
1.11	Issuing Bank timed out
1.12	Card limit exceeded
1.13	Insufficient funds
1.14	Transaction type not allowed
1.15	Issuing bank not found
1.16	Invalid format or field

Status workflows

The status of a successful transaction with ProPay varies, depending on the options you choose.


Sale	When `isAuthOnly` is `false`, successful sale transactions will have the following statuses: pending* or authorized settled
Auth only	When `isAuthOnly` is `true`, successful sale transactions will have the following status: authOnly
Capture	Successful capture transactions will have the following statuses: pending* or authorized settled
Void	Successful void transactions will have the following status: voided
Refund	Successful refund transactions will have the following statuses: pending* or authorized settled

*Pending status displays as "authorized" or "AUTHORIZED" in the Nexio Dashboard; it displays as 10, meaning "authorized", in the response when querying transactions (for more information about transactionStatus, see the appropriate transactionStatus table).

If you have any additional questions or feedback, contact us.

ProPay integration guide