2.0 Credit Card Simulator

Operational

Security Token:

MID(e.g. 123):

Amount (e.g. 10.00):

Cardholder Name:

Card Number (e.g. 4506 2647 3306 8251):

Card Expiry (e.g. mmyy, 1220):

Card CVV (e.g. 123):

Description:

JSON

Tab Delimited

POST

Test URL:

https://secure.e-registernow.com/cgi-bin/accept.dll?TOKEN=&MID=123&XXXAMOUNT=
&XXXCARDHOLDERNAME=&XXXCARDNUMBER=&XXXEXPIRY=
&XXXCVV=&FORMATSTYLE=JSON&apiButton=POST&state=CARDSIMULATOR

URL Breakdown

• TOKEN is the security token that you get from the authentication calls.
• MID is the M account number you would like to simulate the transaction through.
• XXXAMOUNT is the transaction amount you would like to simulate.
• XXXCARDHOLDERNAME is the name of the credit card holder.
• XXXCARDNUMBER is the credit card number.
• XXXEXPIRY is the expiry date of the credit card.
• XXXCVV is the verification number on the back of the credit card.
• XXXDESC is a 90 char description of the transaction
• FORMATSTYLE(JSON or Tab Delimited) is the format you want the return to be in.

About Call:

• This simulator does not process transactions through any financial institution or the eRegisterNow system, it just performs some checks on the credit card info you submit, This simulator is completely isolated from everything.
• The response from the eRegisterNow server returns JSON or TAB delimited.
• The credit card must pass the mod-10 Luhn rule. (e.g. https://bestccgen.com/visa-card-generator)
• This simulator returns approved or declined for given any card number.
• Negative Amounts are NOT allowed.
• Test Cards, these card values created test transactions which are deleted each night at 1AM.
  • Approval - 4444 0000  0000  0000
  • Decline - 4003  0505  0004  0005

Errors:

• 869: invalid security token
• 872: invalid amount
• 874: invalid card number
• 870: invalid cvv
• 871: invalid expiry date
• 873: card must be visa, master card, or American express
• 876: card does not pass Luhn's Rule

2.1 Sale Transaction

Operational

Security Token:

MID(e.g. 123):

Amount (e.g. 10.00):

Cardholder Name:

Cardholder Number (e.g. 4506 2647 3306 8251):

Card Expiry (e.g. mmyy, 1220):

Card CVV (e.g. 123):

Description:

JSON

Tab Delimited

POST

URL Breakdown

• TOKEN is the security token that you get from the authentication calls.
• MID is the M account number you would like to simulate the transaction through.
• XXXAMOUNT is the transaction amount you would like to simulate.
• XXXCARDHOLDERNAME is the name of the credit card holder.
• XXXCARDNUMBER is the credit card number.
• XXXEXPIRY is the expiry date of the credit card.
• XXXCVV is the verification number on the back of the credit card.
• XXXDESC is a 90 char description of the transaction
• FORMATSTYLE(JSON or Tab Delimited) is the format you want the return to be in.

About Call:

• The response from the eRegisterNow server returns JSON or TAB delimited.
• This call performs a real-time credit card SALE through the specified an M-account
• Negative Amounts are NOT allowed.

Errors:

2.2 Return Transaction

Operational

Security Token:

MID(e.g. 123):

Reference Number (e.g. 21123456):

TR_ID(e.g. 123):

Refund Amount (e.g. 10.00):

JSON

Tab Delimited

POST

URL Breakdown

• TOKEN is the security token that you get from the authentication calls.
• MID is the M account number you would like to simulate the transaction through.
• RREF is the
• XXXAMOUNT is the transaction amount you would like to simulate.
• FORMATSTYLE(JSON or Tab Delimited) is the format you want the return to be in.

About Call:

• The response from the eRegisterNow server returns JSON or TAB delimited.
• This call performs a real-time credit card RETURN through the specified an M-account
• Negative Amounts are NOT allowed.
• If the date of the original SALE is the same as the DATE of this return, a VOID transaction will occur.
• The refund amounts may not exceed the total original sale amount.

Errors: