×
Menu

BPoint Payment Gateway

 
This page details the inputs, secure inputs and outputs available for the BPoint Logic Item, how to complete each field, and an external link to the BPoint integration documentation.
 
PCI Pal must check any payment gateway integrations prior to going live.  The documentation disclaimer (which applies throughout this guide) should be read before commencing any configuration of payment gateways.
 

Inputs

Input Fields
Required
Character Limits/
Required Input
Description
username
No (C)
n/a
Unique username provided to the client by BPoint
merchantId
No (C)
n/a
Unique merchant ID provided to the client by BPoint
password
No (C)
n/a
Unique password provided to the client by BPoint
WebHookUrl
No
n/a
Merchant web hook handler URL
RedirectionUrl
No
n/a
Merchant receipt redirection URL
TestMode
No
boolean
Whether or not test mode is being used, values are:
- true
- false
Action
Yes
n/a
The following must be used to specify the type of transaction:
- payment
- unmatched_refund
- preauth
- capture
BillerCode
No
50 chars
Biller code for the transaction
MerchantReference
No
50 chars
Reference that is for internal use only
Crn1
Yes
50 chars
This field should be unique for each payment
Crn2
No
50 chars
Additional crn field
Crn3
No
50 chars
Additional crn field
Currency
Yes
3 chars
The three-character currency for the transaction, e.g. GBP, EUR, USD, AUD
Amount
Yes
n/a
The amount for the transaction
AmountOriginal
No
n/a
Total payment amount without surcharge - this field is for information and reporting only and does not alter the value of the transaction (as specified by Amount)
AmountSurcharge
No
n/a
Surcharge amount for payment - this field is for information and reporting only and does not alter the value of the transaction (as specified by Amount)
TokenisationMode
No
1 num
Determines whether or not tokenisation of the payment instrument will occur:
- 0 Default
- 1 Do not tokenise
- 2 Tokenise if customer opts in
- 3 Always tokenise
AmexExpressCheckout
No
20 chars
A person name's infix, if applicable
BypassThreeDS
No
4 chars
Should always be set to true, PCI Pal do not support 3DS.
SubType
Yes
9 chars
Defines a sub type for transaction:
- single Used for one-off transactions
- recurring Used when the merchant regularly debits the account, e.g. monthly billing. Note, recurring payments are only supported for Visa, MasterCard, American Express, Diner's Club and JCB cards
CustomerDateOfBirth
No
8 num
Date of birth in the format DDMMYYYY
CustomerFirstName
No
n/a
First name
CustomerLastName
No
n/a
Last name
CustomerMiddleName
No
n/a
Middle name
CustomerSalutation
No
n/a
Salutation
CustomerEmailAddress
No
n/a
Email Address
CustomerFaxNumber
No
n/a
Fax Number
CustomerHomePhoneNumber
No
n/a
Customer Home Phone Number
CustomerMobilePhoneNumber
No
n/a
Customer Mobile Phone Number
CustomerWorkPhoneNumber
No
n/a
Customer Work Phone Number
CustomerAddressLine1
Yes
n/a
First line of address
CustomerAddressLine2
No
n/a
Second line of address
CustomerAddressLine3
No
n/a
Third line of address
CustomerCity
No
n/a
City of the address
CustomerCountryCode
No
n/a
Country Code of the address
CustomerPostCode
No
n/a
Post code of the address
CustomerState
No
n/a
State of the address
CustomerComments
No
n/a
Comment regarding to the customer information
ShippingDateOfBirth
No
8 num
Date of birth in the format DDMMYYYY
ShippingFirstName
No
n/a
First name
ShippingLastName
No
n/a
Last name
ShippingMiddleName
No
n/a
Middle name
ShippingSalutation
No
n/a
Salutation
ShippingEmailAddress
No
n/a
Email Address
ShippingFaxNumber
No
n/a
Fax Number
ShippingHomePhoneNumber
No
n/a
Shipping Home Phone Number
ShippingMobilePhoneNumber
No
n/a
Shipping Mobile Phone Number
ShippingWorkPhoneNumber
No
n/a
Shipping Work Phone Number
ShippingAddressLine1
No
n/a
First line of address
ShippingAddressLine2
No
n/a
Second line of address
ShippingAddressLine3
No
n/a
Third line of address
ShippingCity
No
n/a
City of the address
ShippingCountryCode
No
n/a
Country Code of the address
ShippingPostCode
No
n/a
Post code of the address
ShippingState
No
n/a
State of the address
ShippingComments
No
n/a
Comment regarding to the shipping information
BillingDateOfBirth
No
8 num
Date of birth in the format DDMMYYYY
BillingFirstName
No
n/a
First name
BillingLastName
No
n/a
Last name
BillingMiddleName
No
n/a
Middle name
BillingSalutation
No
n/a
Salutation
BillingEmailAddress
No
n/a
Email Address
BillingFaxNumber
No
n/a
Fax Number
BillingHomePhoneNumber
No
n/a
Billing Home Phone Number
BillingMobilePhoneNumber
No
n/a
Billing Mobile Phone Number
BillingWorkPhoneNumber
No
n/a
Billing Work Phone Number
BillingAddressLine1
No
n/a
First line of address
BillingAddressLine2
No
n/a
Second line of address
BillingAddressLine3
No
n/a
Third line of address
BillingCity
No
n/a
City of the address
BillingCountryCode
No
n/a
Country Code of the address
BillingPostCode
No
n/a
Post code of the address
BillingState
No
n/a
State of the address
BillingComments
No
n/a
Comment regarding to the billing information
ShippingMethod
Yes
n/a
Method of shipping for the item:
- Next_Day_Service
- Two_Day_Service
- Three_Day_Service
- Low_Cost_Carrier
- Customer_Choice
- Military
- Collect_At_Store
- Other
CardHolderName
No
50 chars
Cardholder name
OriginalTxnNumber
No
50 chars
Used for refunds, reversals and captures.
 
For refunds: transaction number of the payment or capture being refunded.
For reversals: transaction number of the payment, refund, preauth, capture or unmatched_refund that is being reversed.
For captures: transaction number of preauth that is being captured.
 
MANDATORY when action is refund, reversal or capture, otherwise NOT REQUIRED and will be ignored
EmailAddress
No
n/a
Customer email address
 
DVToken
Auth key Only
n/a
System generated dvtoken. Tokens can be used in place of a card number to process transactions using the payment details saved for that dvtoken Only returned if tokenisation is requested
UpdateDVTokenExpiryDate
Auth key Only
boolean
true or false value
TokeniseTxnCheckBoxDefaultValue
Auth key Only
boolean
Sets the default value for the tokenisation check box
ApiKey
No
 
 
RedirectUrl
Auth key Only
 
Merchant receipt redirection URL
paymentType
Yes
n/a
This should be set to either:
- twoParty
- threeParty
- authKey
Type
Yes
n/a
Needs to be set to either:
- callcentre
- ivr
- telephoneorder
 
(C) - If the Logic Item Username and Password is not filled in, this will be required.
 
Secure Inputs
Input Fields
Required
Character Limits/
Required Input
Description
CardNumber
Yes
19 chars
Secure input of the card number
ExpiryDate
Yes
4 chars
Secure input of the card expiry - in the format MMYY
Cvn
Yes
3 or 4 chars
Secure input of the card CVV, either three or four digits long depending on the card
 
Outputs
Output Fields
Description
responseCode
Numeric code returned from the API to indicate whether request was successful (0) or not (any non 0 value)
responseText
Text returned from the API to provide the description of the response
Action
The Action type of the transaction
Amount
Total transaction amount in the lowest denomination for the currency. If AUD use 12000 for $120.00. If JPY use 120 for ¥120
AmountOriginal
Base transaction amount in the lowest denomination for the currency (without surcharge)
AmountSurcharge
Surcharge amount in the lowest denomination for the currency
AuthoriseId
AuthoriseId issued by the Acquirer for approved transactions. Not all Acquirers return the AuthoriseId even if the transaction is approved
BankResponseCode
Response code returned from the issuing bank
BillerCode
Biller code for the payment
CardType
Type of card used to process transaction -
AX American Express
DC Diners Club
JC JCB Card
MC MasterCard
UP China Union Pay
VC Visa
Crn1
Additional information passed in to the request
Crn2
Additional information passed in to the request
Crn3
Additional information passed in to the request
Currency
Currency of the transaction
DVToken
System generated dvtoken
EmailAddress
Customer's email address
MerchantNumber
MerchantNumber
OriginalTxnNumber
Returned for refunds, reversals and captures. Transaction number of the original transaction
MerchantReference
Reference that is for internal use only
RRN
Retrieval reference number
ReceiptNumber
Receipt number
CVNResultCode
Returned by the Card Issuer to show the level of match that occurred with the CVN check
M Valid or matched CVN
S Merchant indicates CVN not present on card
P CVN Not Processed
U Card issuer is not registered and/or certified
N Code invalid or not matched
Unsupported Acquiring institution does not support CVN
SettlementDate
Date of settlement. In YYYYMMDD format
Source
Transaction origin:
api Transaction submitted using the API.
callcentre Transaction submitted via a call center
customerportal Transaction submitted via the consumer portal
internet Transaction submitted through the hosted payment page
invoiceportal Reserved for future use
ishop Tranasction submitted through an iShop
ivr Transaction submitted through an IVR
backoffice Transaction submitted through the Merchant Back Office
mobilebackoffice Transaction submitted through Merchant Mobile Back Office
sftp Transaction submitted via SFTP
unknown Transaction submitted via an unknown channel
SubType
Transaction sub type:
single Used for one-off transactions
recurring Used when the merchant regularly debits the account, e.g. monthly billing. Note, recurring payments are only supported for Visa, MasterCard, American Express, Diner's Club and JCB cards
TxnNumber
Unique transaction number
Type
Transaction type:
callcentre Used for a call centre transaction. Transaction is flagged as a telephone order to the Issuer
ivr Used for an automated phone (IVR) transaction. Transaction is flagged as a telephone order to the Issuer
telephoneorder Used for a telephone order transaction. Transactions is flagged as a telephone order to the Issuer
IsCVNPresent
Indicates whether CVN was present
IsTestTxn
Flag indicating the transaction was processed as a test transaction
IsThreeDS
Indicates whether transaction was subject to 3D Secure verification
StoreCard
Flag to indicate whether the cardholder agreed to save their card details.
CardHolderName
Card Holder Name if present
MaskedCardNumber
The Masked Card number for card payments or dvtoken for dvtoken payments
ExpiryDate
Card expiry date In MMYY format
AuthKey
Unique key that the merchant must use when invoking the "Process Transaction" operation using Browser integration method. The AuthKey is returned only if the API response code indicates success
RedirectionUrl
Merchant receipt redirection URL
ResultKey
This is the result key that you will have to submit to retrieve the transaction result and present the receipt to the customer,"Retrieve Transaction Result"
pcipal.errorMessage
PCI Pal Specific Error Message.  If anything goes wrong in the sending of a request, our internal error handling will respond with a message on the output of the flow
 
BPoint Logic Item
The BPoint Logic Item contains the following properties:
 
BPoint Payment Gateway
 
1

Username

User Name given to the client by BPoint in order to authenticate a payment.
2

Password

Password given to the client by BPoint in order to authenticate a payment.
3

Merchant ID

Merchant ID given to the client by BPoint in order to authenticate a payment.

Success Result Code

4Each gateway has its own unique selection of status codes on a request back from the gateway - for BPoint, this is:
- 0
 
This must be set in order for our internal logging processes to notice that the payment has come back with the expected response.
5

Select Endpoint

  For added security the BPoint endpoints have been hardcoded into the integration.  Test or Live needs to be selected from the Select Endpoint drop down list, depending on the transaction being conducted.
 
Further information can be found by viewing the integration documentation:
 
The help manual was created with Dr.Explain