Approve payment
Payments
The payments REST services allow you to initiate a payment, retrieve the payment details or perform specific actions like refunding or requesting capture of a payment. A payment is identified by its paymentId. Some payment products allow a two step approach allowing you to control when the authorization takes place separate from when the funds are actually captured.
Request
When you are ready to capture the funds on a payment with a PENDING_APPROVAL state you can call this API. This API will request the transaction to be captured. Depending on the payment product and the 3rd party used to process the payment this is done in real-time or in a more off-line, batch-like fashion.
Based on how your account has been configured, transactions will require this second step before the funds are actually captured.
PENDING_APPROVAL is a common status only with card and direct debit transactions. Only with special configuration is it possible to also have this for PayPal transactions.
Note that the PENDING_APPROVAL status is used for payments that only allow a single capture. Such a capture will update the status of the payment. The similar PENDING_CAPTURE status is used for payments that allow multiple captures. These captures can be done using the capture payment API and result in a new Capture object. In case you want to capture a lower amount then the authorized amount you can specify the amount you would like to be captured. It is also possible to provide some updated information (airline data, references) and/or details on the signed direct debit mandate.
PayloadApprovePaymentRequest
Properties
|
|||
Property | Type | Required | Details |
---|---|---|---|
amount | integer (12) | no | read close |
close
DescriptionIn case you want to approve the capture of a different lower amount you can specify this here (specified in cents, where single digit currencies are presumed to have 2 digits)
|
|||
object | no | read close | |
close
DescriptionObject that holds non-SEPA Direct Debit specific input data
|
|||
close
DescriptionThe desired date for the collection
Format: YYYYMMDD |
|||
close
DescriptionToken containing tokenized bank account details
|
|||
object | no | read close | |
close
DescriptionObject that holds SEPA Direct Debit specific input data
|
|||
close
DescriptionThe desired date for the collection
Format: YYYYMMDD |
|||
close
DescriptionToken containing tokenized bank account details
|
|||
object | no | read close | |
close
DescriptionObject containing additional input on the order
|
|||
close
DescriptionNumeric code identifying the agent
|
|||
close
DescriptionAirline numeric code
|
|||
close
DescriptionDate of the Flight
Format: YYYYMMDD Depends on:Required by the TechProcess platform for airline merchants.
|
|||
close
DescriptionObject that holds the data on the individual legs of the ticket
Depends on:Required by the TechProcess platform for airline merchants.
|
|||
close
DescriptionReservation Booking Designator
|
|||
close
DescriptionArrival airport/city code
Depends on:Required by the TechProcess platform for airline merchants.
|
|||
close
DescriptionThe arrival time in the local time zone
Format: HH:MM |
|||
close
DescriptionIATA carrier code
|
|||
close
DescriptionIdentifying number of a ticket issued to a passenger in conjunction with this ticket and that constitutes a single contract of carriage
|
|||
close
DescriptionThe coupon number associated with this leg of the trip. A ticket can contain several legs of travel, and each leg of travel requires a separate coupon
|
|||
close
DescriptionDate of the leg
Format: YYYYMMDD Depends on:Required by the TechProcess platform for airline merchants.
|
|||
close
DescriptionThe departure time in the local time at the departure airport
Format: HH:MM Depends on:Required for PayPal (840) when Airline data is submitted
|
|||
close
DescriptionAn endorsement can be an agency-added notation or a mandatory government required notation, such as value-added tax. A restriction is a limitation based on the type of fare, such as a ticket with a 3-day minimum stay
|
|||
close
DescriptionNew ticket number that is issued when a ticket is exchanged
|
|||
close
DescriptionFare of this leg
|
|||
close
DescriptionFare Basis/Ticket Designator
|
|||
close
DescriptionFee for this leg of the trip
|
|||
close
DescriptionThe flight number assigned by the airline carrier with no leading spaces
Should be a numeric string Depends on:Required for PayPal (840) when Airline data is submitted
|
|||
close
DescriptionSequence number of the flight leg
|
|||
close
DescriptionOrigin airport/city code
Depends on:Required by the TechProcess platform for airline merchants.
|
|||
close
DescriptionPassengerClass if this leg
|
|||
close
Deprecated:
Use passengerClass instead
DescriptionServiceClass of this leg (this property is used for fraud screening on the Ogone Payment Platform).
Possible values are:
|
|||
close
DescriptionPossible values are:
Depends on:Required for PayPal (840) when Airline data is submitted
|
|||
close
DescriptionTaxes for this leg of the trip
|
|||
close
DescriptionAirline tracing number
|
|||
close
Description
|
|||
close
Deprecated:
Use order.customer.accountType instead
Description
|
|||
close
Description
|
|||
close
Description
|
|||
close
DescriptionThis is the date of issue recorded in the airline system
In a case of multiple issuances of the same ticket to a cardholder, you should use the last ticket date.
Format: YYYYMMDD |
|||
close
DescriptionYour ID of the customer in the context of the airline data
|
|||
close
DescriptionName of the airline
|
|||
close
DescriptionTotal number of passengers in the party. If the the property numberInParty is not present, then the number of passengers will be used on the WL Online Payment Acceptance Platform.
|
|||
close
DescriptionName of passenger
Depends on:Required by the TechProcess platform for airline merchants.
|
|||
close
DescriptionObject that holds the data on the individual passengers (this object is used for fraud screening on the Ogone Payment Platform)
|
|||
close
DescriptionFirst name of the passenger (this property is used for fraud screening on the Ogone Payment Platform)
|
|||
close
DescriptionSurname of the passenger (this property is used for fraud screening on the Ogone Payment Platform)
|
|||
close
DescriptionSurname prefix of the passenger (this property is used for fraud screening on the Ogone Payment Platform)
|
|||
close
DescriptionTitle of the passenger (this property is used for fraud screening on the Ogone Payment Platform)
|
|||
close
DescriptionPlace of issue
For sales in the US the last two characters (pos 14-15) must be the US state code. |
|||
close
DescriptionPassenger name record
Depends on:Required by the TechProcess platform for airline merchants.
|
|||
close
DescriptionIATA point of sale name
|
|||
close
Descriptioncity code of the point of sale
|
|||
close
DescriptionPossible values:
|
|||
close
DescriptionThe ticket or document number. On the Ogone Payment Platform and the GlobalCollect Payment Platform it contains:
|
|||
close
DescriptionTotal fare for all legs on the ticket, excluding taxes and fees. If multiple tickets are purchased, this is the total fare for all tickets
|
|||
close
DescriptionTotal fee for all legs on the ticket. If multiple tickets are purchased, this is the total fee for all tickets
|
|||
close
DescriptionTotal taxes for all legs on the ticket. If multiple tickets are purchased, this is the total taxes for all tickets
|
|||
close
DescriptionName of the travel agency issuing the ticket. For direct airline integration, leave this property blank on the Ogone Payment Platform.
|
|||
close
DescriptionObject that holds lodging related charges
|
|||
close
DescriptionAmount of additional charges associated with the stay of the guest.
Note: The currencyCode is presumed to be identical to the order.amountOfMoney.currencyCode. |
|||
close
DescriptionCurrency for Charge amount. The code should be in 3 letter ISO format.
|
|||
close
DescriptionType of additional charges associated with the stay of the guest.
Allowed values:
|
|||
close
DescriptionThe date the guest checks into (or plans to check in to) the facility.
Format: YYYYMMDD |
|||
close
DescriptionThe date the guest checks out of (or plans to check out of) the facility.
Format: YYYYMMDD |
|||
close
DescriptionThe Lodging Folio Number assigned to the itemized statement of charges and credits associated with this lodging stay, which can be any combination of characters and numerals defined by the Merchant or authorized Third Party Processor.
|
|||
close
DescriptionIndicates whether the room reservation is confirmed.
|
|||
close
DescriptionDefines whether or not the facility conforms to the requirements of the Hotel and Motel Fire Safety Act of 1990, or similar legislation.
|
|||
close
DescriptionIndicate if this the customer is a no show case. In such case, the lodging property can charge a no show fee.
|
|||
close
DescriptionIndicated the preference of the customer for a smoking or non-smoking room.
|
|||
close
DescriptionThe total number of adult guests staying (or planning to stay) at the facility (i.e., all booked rooms)
|
|||
close
DescriptionThe number of nights for the lodging stay
|
|||
close
DescriptionThe number of rooms rented for the lodging stay
|
|||
close
DescriptionCode that corresponds to the category of lodging charges detailed in this message.
Allowed values:
|
|||
close
DescriptionThe international customer service phone number of the facility
|
|||
close
DescriptionThe local phone number of the facility in an international phone number format
|
|||
close
DescriptionName of the person or business entity charged for the reservation and/or lodging stay
|
|||
close
DescriptionObject that holds lodging related room data
|
|||
close
DescriptionDaily room rate exclusive of any taxes and fees
Note: The currencyCode is presumed to be identical to the order.amountOfMoney.currencyCode. |
|||
close
DescriptionCurrency for Daily room rate. The code should be in 3 letter ISO format
|
|||
close
DescriptionDaily room tax
Note: The currencyCode is presumed to be identical to the order.amountOfMoney.currencyCode. |
|||
close
DescriptionCurrency for Daily room tax. The code should be in 3 letter ISO format
|
|||
close
DescriptionNumber of nights charged at the rate in the dailyRoomRate property
|
|||
close
DescriptionLocation of the room within the facility, e.g. Park or Garden etc.
|
|||
close
DescriptionRoom number
|
|||
close
DescriptionSize of bed, e.g., king, queen, double.
|
|||
close
DescriptionDescribes the type of room, e.g., standard, deluxe, suite.
|
|||
close
DescriptionObject containing data related to the customer
|
|||
close
DescriptionType of the customer account that is used to place this order. Can have one of the following values:
|
|||
close
DescriptionObject that holds all reference properties that are linked to this transaction
|
|||
close
DescriptionYour (unique) reference for the transaction that you can use to reconcile our report files
|
|||
Property | Type | Required | Details |
Request example
This scenario you will probably use the most
-
var body = { "directDebitPaymentMethodSpecificInput" : { "token" : "bfa8a7e4-4530-455a-858d-204ba2afb77e", "dateCollect" : "20150201" }, "order" : { "references" : { "merchantReference" : "AcmeOrder0001" } }, "amount" : 2980 }; const sdkResponse = await client.v1.payments.approve("merchantId", "paymentId", body); // sdkResponse has the following properties: // - status: the HTTP status code // - body: the response body // - isSuccess: true if the call was successful, // or false if the Worldline Global Collect platform returned an error response
Responses
Please find below an overview of the possible responses.
Response 200 - OKPaymentApprovalResponse
The capture request was processed correctly. The new state of the payment can be found in the response.
Properties
|
|||
Property | Type | Required | Details |
---|---|---|---|
object | no | read close | |
close
DescriptionObject containing additional card payment method specific details
|
|||
close
DescriptionResult of the authorization reversal request
Possible values are:
|
|||
object | no | read close | |
close
DescriptionObject containing additional mobile payment method specific details
|
|||
close
DescriptionResult of the authorization reversal request
Possible values are:
|
|||
object | no | read close | |
close
DescriptionHosted Checkout specific information. Populated if the payment was created on the GlobalCollect platform through a Hosted Checkout.
|
|||
close
DescriptionThe ID of the Hosted Checkout Session in which the payment was made.
|
|||
close
DescriptionUsing the Configuration Center it is possible to create multiple variations of your MyCheckout payment pages. By specifying a specific variant you can force the use of another variant then the default. This allows you to test out the effect of certain changes to your hosted mandate pages in a controlled manner. Please note that you need to specify the ID of the variant.
|
|||
close
DescriptionOur unique payment transaction identifier.
|
|||
close
DescriptionObject containing amount and ISO currency code attributes
|
|||
close
DescriptionAmount in cents and always having 2 decimals
|
|||
close
DescriptionThree-letter ISO currency code representing the currency for the amount
|
|||
close
DescriptionAmount that has been paid
|
|||
close
DescriptionAmount that has been reversed
|
|||
close
DescriptionObject containing the bank transfer payment method details
|
|||
close
DescriptionThis object contains the results of the Cybersource Decision Manager assessment. Cybersource is a fraud detection tool leveraging data networks, configurable rules, intelligence, and device fingerprinting to identify risky transactions.
|
|||
close
DescriptionName of the clause within the applied policy that was triggered during the evaluation of this transaction.
|
|||
close
DescriptionResult of the Cybersource Decision Manager check. This contains the normalized fraud score from a scale of 0 to 100. A higher score indicates an increased risk of fraud.
|
|||
close
DescriptionName of the policy that was applied during the evaluation of this transaction.
|
|||
close
DescriptionList of one or more reason codes.
|
|||
close
DescriptionResults from the fraud prevention check. Possible values are:
|
|||
close
DescriptionObject containing device fingerprinting details from InAuth
|
|||
close
DescriptionThe type of device used by the customer. Example values:
|
|||
close
DescriptionThis is the device fingerprint value. Based on the amount of data that the device fingerprint collector script was able to collect, this will be a proxy ID for the device used by the customer.
|
|||
close
DescriptionThe score calculated on the basis of Anomalies, Velocity, Location, Integrity, List-Based, and Device Reputation. Range of the score is between 0 and 100. A lower value is better.
|
|||
close
DescriptionThe true IP address as determined by inAuth. This might be different from the IP address that you are seeing on your side due to the proxy piercing technology deployed by inAuth.
|
|||
close
DescriptionThe country of the customer based on the location of the True IP Address determined by inAuth.
|
|||
close
DescriptionThis object contains the results of Microsoft Fraud Protection risk assessment. Microsoft collects transaction data points and uses Adaptive AI that continuously learns to protect you against payment fraud, and the device fingerprinting details from the Microsoft Device Fingerprinting service.
|
|||
close
DescriptionName of the clause within the applied policy that was triggered during the evaluation of this transaction.
|
|||
close
DescriptionThe country of the customer determined by Microsoft Device Fingerprinting.
|
|||
close
DescriptionThis is the device fingerprint value. Based on the amount of data that the device fingerprint collector script was able to collect, this will be a proxy ID for the device used by the customer.
|
|||
close
DescriptionResult of the Microsoft Fraud Protection check. This contains the normalized fraud score from a scale of 0 to 100. A higher score indicates an increased risk of fraud.
|
|||
close
DescriptionName of the policy that was applied on during the evaluation of this transaction.
|
|||
close
DescriptionList of one or more reason codes.
|
|||
close
DescriptionThe true IP address as determined by Microsoft Device Fingerprinting.
|
|||
close
DescriptionThe type of device used by the customer.
|
|||
close
DescriptionPayment product identifier
Please see payment products for a full overview of possible values. |
|||
close
DescriptionObject containing the card payment method details
|
|||
close
DescriptionCard Authorization code as returned by the acquirer
|
|||
close
DescriptionThe complete credit/debit card number
|
|||
close
DescriptionThe card holder's name on the card. Minimum length of 2, maximum length of 51 characters.
|
|||
close
DescriptionExpiry date of the card
Format: MMYY |
|||
close
DescriptionFraud results contained in the CardFraudResults object
|
|||
close
DescriptionResult of the Address Verification Service checks. Possible values are:
|
|||
close
DescriptionResult of the Card Verification Value checks. Possible values are:
|
|||
close
DescriptionThis object contains the results of the Cybersource Decision Manager assessment. Cybersource is a fraud detection tool leveraging data networks, configurable rules, intelligence, and device fingerprinting to identify risky transactions.
|
|||
close
DescriptionName of the clause within the applied policy that was triggered during the evaluation of this transaction.
|
|||
close
DescriptionResult of the Cybersource Decision Manager check. This contains the normalized fraud score from a scale of 0 to 100. A higher score indicates an increased risk of fraud.
|
|||
close
DescriptionName of the policy that was applied during the evaluation of this transaction.
|
|||
close
DescriptionList of one or more reason codes.
|
|||
close
DescriptionResulting advice of the fraud prevention checks. Possible values are:
|
|||
close
DescriptionResults of Fraugster fraud prevention check. Fraugster collects transaction data points such as name, email address, billing, etc. to analyze whether or not the transaction is fraudulent.
|
|||
close
DescriptionResult of the Fraugster check
Contains the investigation points used during the evaluation
|
|||
close
DescriptionResult of the Fraugster check
Contains the overall Fraud score which is an integer between 0 and 99
|
|||
close
DescriptionObject containing device fingerprinting details from InAuth
|
|||
close
DescriptionThe type of device used by the customer. Example values:
|
|||
close
DescriptionThis is the device fingerprint value. Based on the amount of data that the device fingerprint collector script was able to collect, this will be a proxy ID for the device used by the customer.
|
|||
close
DescriptionThe score calculated on the basis of Anomalies, Velocity, Location, Integrity, List-Based, and Device Reputation. Range of the score is between 0 and 100. A lower value is better.
|
|||
close
DescriptionThe true IP address as determined by inAuth. This might be different from the IP address that you are seeing on your side due to the proxy piercing technology deployed by inAuth.
|
|||
close
DescriptionThe country of the customer based on the location of the True IP Address determined by inAuth.
|
|||
close
DescriptionThis object contains the results of Microsoft Fraud Protection risk assessment. Microsoft collects transaction data points and uses Adaptive AI that continuously learns to protect you against payment fraud, and the device fingerprinting details from the Microsoft Device Fingerprinting service.
|
|||
close
DescriptionName of the clause within the applied policy that was triggered during the evaluation of this transaction.
|
|||
close
DescriptionThe country of the customer determined by Microsoft Device Fingerprinting.
|
|||
close
DescriptionThis is the device fingerprint value. Based on the amount of data that the device fingerprint collector script was able to collect, this will be a proxy ID for the device used by the customer.
|
|||
close
DescriptionResult of the Microsoft Fraud Protection check. This contains the normalized fraud score from a scale of 0 to 100. A higher score indicates an increased risk of fraud.
|
|||
close
DescriptionName of the policy that was applied on during the evaluation of this transaction.
|
|||
close
DescriptionList of one or more reason codes.
|
|||
close
DescriptionThe true IP address as determined by Microsoft Device Fingerprinting.
|
|||
close
DescriptionThe type of device used by the customer.
|
|||
close
DescriptionAdditional response data returned by RetailDecisions
|
|||
close
DescriptionResult of the fraud service.
Provides additional information about the fraud result
|
|||
close
DescriptionReturns the raw score of the neural
|
|||
close
DescriptionResult of the fraud service
Represent sets of fraud rules returned during the evaluation of the transaction
|
|||
close
DescriptionThe unique scheme transactionId of the initial transaction that was performed with SCA.
Should be stored by the merchant to allow it to be submitted in future transactions. |
|||
close
DescriptionObject holding data that describes a network token.
|
|||
close
DescriptionThe network token alternative for the full Permanent Account Number. To receive a non-obfuscated network token please contact your account manager.
|
|||
close
DescriptionThe expiry date of the network token.
|
|||
close
DescriptionA unique identifier that can be used with Visa Token Service (VTS) or Mastercard Digital Enablement Service (MDES) to retrieve token details. It remains valid as long as the token is valid. Note: A prefix "V:" is added to show that this is a network token for a Visa product and "M:" to show that this is a network token for a Mastercard product.
|
|||
close
DescriptionIndicates if a network token was used during the payment.
|
|||
close
DescriptionA unique reference to the primary account number. Payment Account Reference provides a consolidated view of transactions associated with a PAN and its affiliated tokens, making it easier to identify customers and their associated transactions across payment channels.
|
|||
close
DescriptionPayment product identifier
Please see payment products for a full overview of possible values. |
|||
close
DescriptionThe unique scheme transactionId of this transaction.
Should be stored by the merchant to allow it to be submitted in future transactions. Use this value in case the initialSchemeTransactionId property is empty. |
|||
close
DescriptionIdentifier of the authenticated transaction at the ACS/Issuer
|
|||
close
DescriptionExemption code from Carte Bancaire (130) (unknown possible values so far -free format)
|
|||
close
DescriptionThe amount for which this transaction has been authenticated.
|
|||
close
DescriptionAmount in cents and always having 2 decimals
|
|||
close
DescriptionThree-letter ISO currency code representing the currency for the amount
|
|||
close
DescriptionCAVV or AVV result indicating authentication validation value
|
|||
close
DescriptionThe 3-D Secure Directory Server transaction ID that is used for the 3D Authentication
|
|||
close
DescriptionIndicates Authentication validation results returned after AuthenticationValidation
|
|||
close
DescriptionType of strong customer authentication (SCA) exemption that was raised towards the acquirer for this transaction.
|
|||
close
DescriptionThe request exemption could not be granted. The reason why is returned in this property.
|
|||
close
DescriptionType of strong customer authentication (SCA) exemption requested by you for this transaction.
|
|||
close
DescriptionGlobal score calculated by the Carte Bancaire (130) Scoring platform. Possible values from 0 to 99
|
|||
close
DescriptionUniversally unique transaction identifier assigned by the 3-D Secure SDK to identify this transaction.
|
|||
close
DescriptionObject containing data regarding the 3-D Secure authentication
|
|||
close
DescriptionThe ACS Transaction ID for a prior 3-D Secure authenticated transaction (for example, the first recurring transaction that was authenticated with the customer)
|
|||
close
DescriptionMethod of authentication used for this transaction.
Possible values:
|
|||
close
DescriptionTimestamp in UTC (YYYYMMDDHHmm) of the 3-D Secure authentication of this transaction
|
|||
close
DescriptionThe 3-D Secure version used for the authentication.
This property is used in the communication with the acquirer |
|||
close
DescriptionThe 3-D Secure Server transaction ID that is used for the 3-D Secure version 2 Authentication.
|
|||
close
DescriptionTransaction ID for the Authentication
|
|||
close
DescriptionIf a token was used for or created during the payment, then the ID of that token.
|
|||
close
DescriptionObject containing the cash payment method details
|
|||
close
DescriptionThis object contains the results of the Cybersource Decision Manager assessment. Cybersource is a fraud detection tool leveraging data networks, configurable rules, intelligence, and device fingerprinting to identify risky transactions.
|
|||
close
DescriptionName of the clause within the applied policy that was triggered during the evaluation of this transaction.
|
|||
close
DescriptionResult of the Cybersource Decision Manager check. This contains the normalized fraud score from a scale of 0 to 100. A higher score indicates an increased risk of fraud.
|
|||
close
DescriptionName of the policy that was applied during the evaluation of this transaction.
|
|||
close
DescriptionList of one or more reason codes.
|
|||
close
DescriptionResults from the fraud prevention check. Possible values are:
|
|||
close
DescriptionObject containing device fingerprinting details from InAuth
|
|||
close
DescriptionThe type of device used by the customer. Example values:
|
|||
close
DescriptionThis is the device fingerprint value. Based on the amount of data that the device fingerprint collector script was able to collect, this will be a proxy ID for the device used by the customer.
|
|||
close
DescriptionThe score calculated on the basis of Anomalies, Velocity, Location, Integrity, List-Based, and Device Reputation. Range of the score is between 0 and 100. A lower value is better.
|
|||
close
DescriptionThe true IP address as determined by inAuth. This might be different from the IP address that you are seeing on your side due to the proxy piercing technology deployed by inAuth.
|
|||
close
DescriptionThe country of the customer based on the location of the True IP Address determined by inAuth.
|
|||
close
DescriptionThis object contains the results of Microsoft Fraud Protection risk assessment. Microsoft collects transaction data points and uses Adaptive AI that continuously learns to protect you against payment fraud, and the device fingerprinting details from the Microsoft Device Fingerprinting service.
|
|||
close
DescriptionName of the clause within the applied policy that was triggered during the evaluation of this transaction.
|
|||
close
DescriptionThe country of the customer determined by Microsoft Device Fingerprinting.
|
|||
close
DescriptionThis is the device fingerprint value. Based on the amount of data that the device fingerprint collector script was able to collect, this will be a proxy ID for the device used by the customer.
|
|||
close
DescriptionResult of the Microsoft Fraud Protection check. This contains the normalized fraud score from a scale of 0 to 100. A higher score indicates an increased risk of fraud.
|
|||
close
DescriptionName of the policy that was applied on during the evaluation of this transaction.
|
|||
close
DescriptionList of one or more reason codes.
|
|||
close
DescriptionThe true IP address as determined by Microsoft Device Fingerprinting.
|
|||
close
DescriptionThe type of device used by the customer.
|
|||
close
DescriptionPayment product identifier
Please see payment products for a full overview of possible values. |
|||
close
DescriptionObject containing the non SEPA direct debit payment method details
|
|||
close
DescriptionThis object contains the results of the Cybersource Decision Manager assessment. Cybersource is a fraud detection tool leveraging data networks, configurable rules, intelligence, and device fingerprinting to identify risky transactions.
|
|||
close
DescriptionName of the clause within the applied policy that was triggered during the evaluation of this transaction.
|
|||
close
DescriptionResult of the Cybersource Decision Manager check. This contains the normalized fraud score from a scale of 0 to 100. A higher score indicates an increased risk of fraud.
|
|||
close
DescriptionName of the policy that was applied during the evaluation of this transaction.
|
|||
close
DescriptionList of one or more reason codes.
|
|||
close
DescriptionResults from the fraud prevention check. Possible values are:
|
|||
close
DescriptionObject containing device fingerprinting details from InAuth
|
|||
close
DescriptionThe type of device used by the customer. Example values:
|
|||
close
DescriptionThis is the device fingerprint value. Based on the amount of data that the device fingerprint collector script was able to collect, this will be a proxy ID for the device used by the customer.
|
|||
close
DescriptionThe score calculated on the basis of Anomalies, Velocity, Location, Integrity, List-Based, and Device Reputation. Range of the score is between 0 and 100. A lower value is better.
|
|||
close
DescriptionThe true IP address as determined by inAuth. This might be different from the IP address that you are seeing on your side due to the proxy piercing technology deployed by inAuth.
|
|||
close
DescriptionThe country of the customer based on the location of the True IP Address determined by inAuth.
|
|||
close
DescriptionThis object contains the results of Microsoft Fraud Protection risk assessment. Microsoft collects transaction data points and uses Adaptive AI that continuously learns to protect you against payment fraud, and the device fingerprinting details from the Microsoft Device Fingerprinting service.
|
|||
close
DescriptionName of the clause within the applied policy that was triggered during the evaluation of this transaction.
|
|||
close
DescriptionThe country of the customer determined by Microsoft Device Fingerprinting.
|
|||
close
DescriptionThis is the device fingerprint value. Based on the amount of data that the device fingerprint collector script was able to collect, this will be a proxy ID for the device used by the customer.
|
|||
close
DescriptionResult of the Microsoft Fraud Protection check. This contains the normalized fraud score from a scale of 0 to 100. A higher score indicates an increased risk of fraud.
|
|||
close
DescriptionName of the policy that was applied on during the evaluation of this transaction.
|
|||
close
DescriptionList of one or more reason codes.
|
|||
close
DescriptionThe true IP address as determined by Microsoft Device Fingerprinting.
|
|||
close
DescriptionThe type of device used by the customer.
|
|||
close
DescriptionPayment product identifier
Please see payment products for a full overview of possible values. |
|||
close
DescriptionObject containing the e-invoice payment method details
|
|||
close
DescriptionThis object contains the results of the Cybersource Decision Manager assessment. Cybersource is a fraud detection tool leveraging data networks, configurable rules, intelligence, and device fingerprinting to identify risky transactions.
|
|||
close
DescriptionName of the clause within the applied policy that was triggered during the evaluation of this transaction.
|
|||
close
DescriptionResult of the Cybersource Decision Manager check. This contains the normalized fraud score from a scale of 0 to 100. A higher score indicates an increased risk of fraud.
|
|||
close
DescriptionName of the policy that was applied during the evaluation of this transaction.
|
|||
close
DescriptionList of one or more reason codes.
|
|||
close
DescriptionResults from the fraud prevention check. Possible values are:
|
|||
close
DescriptionObject containing device fingerprinting details from InAuth
|
|||
close
DescriptionThe type of device used by the customer. Example values:
|
|||
close
DescriptionThis is the device fingerprint value. Based on the amount of data that the device fingerprint collector script was able to collect, this will be a proxy ID for the device used by the customer.
|
|||
close
DescriptionThe score calculated on the basis of Anomalies, Velocity, Location, Integrity, List-Based, and Device Reputation. Range of the score is between 0 and 100. A lower value is better.
|
|||
close
DescriptionThe true IP address as determined by inAuth. This might be different from the IP address that you are seeing on your side due to the proxy piercing technology deployed by inAuth.
|
|||
close
DescriptionThe country of the customer based on the location of the True IP Address determined by inAuth.
|
|||
close
DescriptionThis object contains the results of Microsoft Fraud Protection risk assessment. Microsoft collects transaction data points and uses Adaptive AI that continuously learns to protect you against payment fraud, and the device fingerprinting details from the Microsoft Device Fingerprinting service.
|
|||
close
DescriptionName of the clause within the applied policy that was triggered during the evaluation of this transaction.
|
|||
close
DescriptionThe country of the customer determined by Microsoft Device Fingerprinting.
|
|||
close
DescriptionThis is the device fingerprint value. Based on the amount of data that the device fingerprint collector script was able to collect, this will be a proxy ID for the device used by the customer.
|
|||
close
DescriptionResult of the Microsoft Fraud Protection check. This contains the normalized fraud score from a scale of 0 to 100. A higher score indicates an increased risk of fraud.
|
|||
close
DescriptionName of the policy that was applied on during the evaluation of this transaction.
|
|||
close
DescriptionList of one or more reason codes.
|
|||
close
DescriptionThe true IP address as determined by Microsoft Device Fingerprinting.
|
|||
close
DescriptionThe type of device used by the customer.
|
|||
close
DescriptionAfterPay Installments (payment product 9000) specific details
|
|||
close
DescriptionThe ID of the installment plan used for the payment.
|
|||
close
DescriptionPayment product identifier
Please see payment products for a full overview of possible values. |
|||
close
DescriptionObject containing the invoice payment method details
|
|||
close
DescriptionThis object contains the results of the Cybersource Decision Manager assessment. Cybersource is a fraud detection tool leveraging data networks, configurable rules, intelligence, and device fingerprinting to identify risky transactions.
|
|||
close
DescriptionName of the clause within the applied policy that was triggered during the evaluation of this transaction.
|
|||
close
DescriptionResult of the Cybersource Decision Manager check. This contains the normalized fraud score from a scale of 0 to 100. A higher score indicates an increased risk of fraud.
|
|||
close
DescriptionName of the policy that was applied during the evaluation of this transaction.
|
|||
close
DescriptionList of one or more reason codes.
|
|||
close
DescriptionResults from the fraud prevention check. Possible values are:
|
|||
close
DescriptionObject containing device fingerprinting details from InAuth
|
|||
close
DescriptionThe type of device used by the customer. Example values:
|
|||
close
DescriptionThis is the device fingerprint value. Based on the amount of data that the device fingerprint collector script was able to collect, this will be a proxy ID for the device used by the customer.
|
|||
close
DescriptionThe score calculated on the basis of Anomalies, Velocity, Location, Integrity, List-Based, and Device Reputation. Range of the score is between 0 and 100. A lower value is better.
|
|||
close
DescriptionThe true IP address as determined by inAuth. This might be different from the IP address that you are seeing on your side due to the proxy piercing technology deployed by inAuth.
|
|||
close
DescriptionThe country of the customer based on the location of the True IP Address determined by inAuth.
|
|||
close
DescriptionThis object contains the results of Microsoft Fraud Protection risk assessment. Microsoft collects transaction data points and uses Adaptive AI that continuously learns to protect you against payment fraud, and the device fingerprinting details from the Microsoft Device Fingerprinting service.
|
|||
close
DescriptionName of the clause within the applied policy that was triggered during the evaluation of this transaction.
|
|||
close
DescriptionThe country of the customer determined by Microsoft Device Fingerprinting.
|
|||
close
DescriptionThis is the device fingerprint value. Based on the amount of data that the device fingerprint collector script was able to collect, this will be a proxy ID for the device used by the customer.
|
|||
close
DescriptionResult of the Microsoft Fraud Protection check. This contains the normalized fraud score from a scale of 0 to 100. A higher score indicates an increased risk of fraud.
|
|||
close
DescriptionName of the policy that was applied on during the evaluation of this transaction.
|
|||
close
DescriptionList of one or more reason codes.
|
|||
close
DescriptionThe true IP address as determined by Microsoft Device Fingerprinting.
|
|||
close
DescriptionThe type of device used by the customer.
|
|||
close
DescriptionPayment product identifier
Please see payment products for a full overview of possible values. |
|||
close
DescriptionObject containing the mobile payment method details
|
|||
close
DescriptionCard Authorization code as returned by the acquirer
|
|||
close
DescriptionFraud results contained in the CardFraudResults object
|
|||
close
DescriptionResult of the Address Verification Service checks. Possible values are:
|
|||
close
DescriptionResult of the Card Verification Value checks. Possible values are:
|
|||
close
DescriptionThis object contains the results of the Cybersource Decision Manager assessment. Cybersource is a fraud detection tool leveraging data networks, configurable rules, intelligence, and device fingerprinting to identify risky transactions.
|
|||
close
DescriptionName of the clause within the applied policy that was triggered during the evaluation of this transaction.
|
|||
close
DescriptionResult of the Cybersource Decision Manager check. This contains the normalized fraud score from a scale of 0 to 100. A higher score indicates an increased risk of fraud.
|
|||
close
DescriptionName of the policy that was applied during the evaluation of this transaction.
|
|||
close
DescriptionList of one or more reason codes.
|
|||
close
DescriptionResulting advice of the fraud prevention checks. Possible values are:
|
|||
close
DescriptionResults of Fraugster fraud prevention check. Fraugster collects transaction data points such as name, email address, billing, etc. to analyze whether or not the transaction is fraudulent.
|
|||
close
DescriptionResult of the Fraugster check
Contains the investigation points used during the evaluation
|
|||
close
DescriptionResult of the Fraugster check
Contains the overall Fraud score which is an integer between 0 and 99
|
|||
close
DescriptionObject containing device fingerprinting details from InAuth
|
|||
close
DescriptionThe type of device used by the customer. Example values:
|
|||
close
DescriptionThis is the device fingerprint value. Based on the amount of data that the device fingerprint collector script was able to collect, this will be a proxy ID for the device used by the customer.
|
|||
close
DescriptionThe score calculated on the basis of Anomalies, Velocity, Location, Integrity, List-Based, and Device Reputation. Range of the score is between 0 and 100. A lower value is better.
|
|||
close
DescriptionThe true IP address as determined by inAuth. This might be different from the IP address that you are seeing on your side due to the proxy piercing technology deployed by inAuth.
|
|||
close
DescriptionThe country of the customer based on the location of the True IP Address determined by inAuth.
|
|||
close
DescriptionThis object contains the results of Microsoft Fraud Protection risk assessment. Microsoft collects transaction data points and uses Adaptive AI that continuously learns to protect you against payment fraud, and the device fingerprinting details from the Microsoft Device Fingerprinting service.
|
|||
close
DescriptionName of the clause within the applied policy that was triggered during the evaluation of this transaction.
|
|||
close
DescriptionThe country of the customer determined by Microsoft Device Fingerprinting.
|
|||
close
DescriptionThis is the device fingerprint value. Based on the amount of data that the device fingerprint collector script was able to collect, this will be a proxy ID for the device used by the customer.
|
|||
close
DescriptionResult of the Microsoft Fraud Protection check. This contains the normalized fraud score from a scale of 0 to 100. A higher score indicates an increased risk of fraud.
|
|||
close
DescriptionName of the policy that was applied on during the evaluation of this transaction.
|
|||
close
DescriptionList of one or more reason codes.
|
|||
close
DescriptionThe true IP address as determined by Microsoft Device Fingerprinting.
|
|||
close
DescriptionThe type of device used by the customer.
|
|||
close
DescriptionAdditional response data returned by RetailDecisions
|
|||
close
DescriptionResult of the fraud service.
Provides additional information about the fraud result
|
|||
close
DescriptionReturns the raw score of the neural
|
|||
close
DescriptionResult of the fraud service
Represent sets of fraud rules returned during the evaluation of the transaction
|
|||
close
DescriptionThe network that was used for the refund
|
|||
close
DescriptionThe obfuscated DPAN. Only the last four digits are visible.
|
|||
close
DescriptionExpiry date of the tokenized card
Format: MMYY |
|||
close
DescriptionPayment product identifier
Please see payment products for a full overview of possible values. |
|||
close
DescriptionIdentifier of the authenticated transaction at the ACS/Issuer
|
|||
close
DescriptionExemption code from Carte Bancaire (130) (unknown possible values so far -free format)
|
|||
close
DescriptionThe amount for which this transaction has been authenticated.
|
|||
close
DescriptionAmount in cents and always having 2 decimals
|
|||
close
DescriptionThree-letter ISO currency code representing the currency for the amount
|
|||
close
DescriptionCAVV or AVV result indicating authentication validation value
|
|||
close
DescriptionThe 3-D Secure Directory Server transaction ID that is used for the 3D Authentication
|
|||
close
DescriptionIndicates Authentication validation results returned after AuthenticationValidation
|
|||
close
DescriptionType of strong customer authentication (SCA) exemption that was raised towards the acquirer for this transaction.
|
|||
close
DescriptionThe request exemption could not be granted. The reason why is returned in this property.
|
|||
close
DescriptionType of strong customer authentication (SCA) exemption requested by you for this transaction.
|
|||
close
DescriptionGlobal score calculated by the Carte Bancaire (130) Scoring platform. Possible values from 0 to 99
|
|||
close
DescriptionUniversally unique transaction identifier assigned by the 3-D Secure SDK to identify this transaction.
|
|||
close
DescriptionObject containing data regarding the 3-D Secure authentication
|
|||
close
DescriptionThe ACS Transaction ID for a prior 3-D Secure authenticated transaction (for example, the first recurring transaction that was authenticated with the customer)
|
|||
close
DescriptionMethod of authentication used for this transaction.
Possible values:
|
|||
close
DescriptionTimestamp in UTC (YYYYMMDDHHmm) of the 3-D Secure authentication of this transaction
|
|||
close
DescriptionThe 3-D Secure version used for the authentication.
This property is used in the communication with the acquirer |
|||
close
DescriptionThe 3-D Secure Server transaction ID that is used for the 3-D Secure version 2 Authentication.
|
|||
close
DescriptionTransaction ID for the Authentication
|
|||
close
DescriptionObject containing the redirect payment product details
|
|||
close
DescriptionObject that holds the Basic Bank Account Number (BBAN) data
|
|||
close
DescriptionName of the account holder
Depends on:Required for Create and Update token calls for ACH (730).
|
|||
close
DescriptionBank account number
Depends on:Required for Direct Debit UK (705) and ACH (730) payments, except when a token has been included in the request that includes this value.
Required for Create and Update token calls. |
|||
close
DescriptionBank code
Depends on:Required for Direct Debit UK (705) and ACH (730) payments, except when a token has been included in the request that includes this value.
Required for Create and Update token calls for ACH (730). |
|||
close
DescriptionName of the bank
|
|||
close
DescriptionBranch code
|
|||
close
DescriptionBank check digit
|
|||
close
DescriptionISO 3166-1 alpha-2 country code of the country where the bank account is held
For UK payouts this value is automatically set to GB as only payouts to UK accounts are supported.
|
|||
close
DescriptionObject containing account holder name and IBAN information
|
|||
close
DescriptionName in which the account is held.
Depends on:Required for the creation of a Payout
Required for Create and Update token calls. |
|||
close
DescriptionThe IBAN is the International Bank Account Number. It is an internationally agreed format for the BBAN and includes the ISO country code and two check digits.
Depends on:Required for the creation of a Payout
Required for Create and Update token. Required for payments with product 9000 (AfterPay Installments) in Austria (AT) and Germany (DE). Required for Create mandate and Create payment with mandate calls |
|||
close
DescriptionThe BIC is the Business Identifier Code, also known as SWIFT or Bank Identifier code. It is a code with an internationally agreed format to Identify a specific bank or even branch. The BIC contains 8 or 11 positions: the first 4 contain the bank code, followed by the country code and location code.
|
|||
close
DescriptionThis object contains the results of the Cybersource Decision Manager assessment. Cybersource is a fraud detection tool leveraging data networks, configurable rules, intelligence, and device fingerprinting to identify risky transactions.
|
|||
close
DescriptionName of the clause within the applied policy that was triggered during the evaluation of this transaction.
|
|||
close
DescriptionResult of the Cybersource Decision Manager check. This contains the normalized fraud score from a scale of 0 to 100. A higher score indicates an increased risk of fraud.
|
|||
close
DescriptionName of the policy that was applied during the evaluation of this transaction.
|
|||
close
DescriptionList of one or more reason codes.
|
|||
close
DescriptionResults from the fraud prevention check. Possible values are:
|
|||
close
DescriptionObject containing device fingerprinting details from InAuth
|
|||
close
DescriptionThe type of device used by the customer. Example values:
|
|||
close
DescriptionThis is the device fingerprint value. Based on the amount of data that the device fingerprint collector script was able to collect, this will be a proxy ID for the device used by the customer.
|
|||
close
DescriptionThe score calculated on the basis of Anomalies, Velocity, Location, Integrity, List-Based, and Device Reputation. Range of the score is between 0 and 100. A lower value is better.
|
|||
close
DescriptionThe true IP address as determined by inAuth. This might be different from the IP address that you are seeing on your side due to the proxy piercing technology deployed by inAuth.
|
|||
close
DescriptionThe country of the customer based on the location of the True IP Address determined by inAuth.
|
|||
close
DescriptionThis object contains the results of Microsoft Fraud Protection risk assessment. Microsoft collects transaction data points and uses Adaptive AI that continuously learns to protect you against payment fraud, and the device fingerprinting details from the Microsoft Device Fingerprinting service.
|
|||
close
DescriptionName of the clause within the applied policy that was triggered during the evaluation of this transaction.
|
|||
close
DescriptionThe country of the customer determined by Microsoft Device Fingerprinting.
|
|||
close
DescriptionThis is the device fingerprint value. Based on the amount of data that the device fingerprint collector script was able to collect, this will be a proxy ID for the device used by the customer.
|
|||
close
DescriptionResult of the Microsoft Fraud Protection check. This contains the normalized fraud score from a scale of 0 to 100. A higher score indicates an increased risk of fraud.
|
|||
close
DescriptionName of the policy that was applied on during the evaluation of this transaction.
|
|||
close
DescriptionList of one or more reason codes.
|
|||
close
DescriptionThe true IP address as determined by Microsoft Device Fingerprinting.
|
|||
close
DescriptionThe type of device used by the customer.
|
|||
close
DescriptionPostFinance Card (payment product 3201) specific details
|
|||
close
DescriptionThe complete credit/debit card number
|
|||
close
DescriptionThe card holder's name on the card. Minimum length of 2, maximum length of 51 characters.
|
|||
close
DescriptionExpiry date of the card
Format: MMYY |
|||
close
DescriptionTrustly (payment product 806) specific details
|
|||
close
DescriptionObject containing the billing address details of the customer
|
|||
close
DescriptionAdditional address information. The additionalInfo is truncated after 10 characters for payments, refunds or payouts that are processed by the WL Online Payment Acceptance platform
|
|||
close
DescriptionCity
Note: For payments with product 1503 the maximum length is not 40 but 20. Depends on:Required by the GlobalCollect platform for Invoice payments (201)
Required by the GlobalCollect platform for Direct Debit UK (705) except when a token has been included in the request that includes this value Required by the GlobalCollect platform for payments with product 9000 (AfterPay Installments) or 9001 (AfterPay Invoice). Required by the WOPA platform for payments with product 6101 (Banco do Brasil), 6102 (Itaú), 6103 (Banrisul), 6104 (Bradesco), 6105 (Pix) or 6107 (PicPay). Required by the TechProcess platform for cross-border merchants. Required by the GlobalCollect platform when address is included in Seller. Required by the GlobalCollect platform for the creation of a Payout. |
|||
close
DescriptionISO 3166-1 alpha-2 country code
Depends on:Required by the GlobalCollect platform.
Required by the TechProcess platform. |
|||
close
DescriptionHouse number. The houseNumber is truncated after 10 characters for payments, refunds or payouts that are processed by the WL Online Payment Acceptance platform
Depends on:Required when address is included in Seller.
Required for 6101 (Banco do Brasil), 6102 (Itaú), 6103 (Banrisul), 6104 (Bradesco), 6105 (Pix) and 6107 (PicPay). |
|||
close
DescriptionFull name of the state or province
Depends on:Required by the TechProcess platform for cross-border merchants.
|
|||
close
DescriptionISO 3166-2 alpha-3 state code
Notes:
Depends on:Required for payments with paymentProductId 1503 (Boleto), 6101 (Banco do Brasil), 6102 (Itaú), 6103 (Banrisul), 6104 (Bradesco), 6105 (Pix) or 6107 (PicPay).
|
|||
close
DescriptionStreetname
Depends on:Required by the GlobalCollect platform for Invoice payments (201)
Required by the GlobalCollect platform for Direct Debit UK (705), except when a token has been included in the request that includes this value. Required by the GlobalCollect platform for payments with product 9000 (AfterPay Installments) or 9001 (AfterPay Invoice). Required by the WOPA platform for payments with product 6101 (Banco do Brasil), 6102 (Itaú), 6103 (Banrisul), 6104 (Bradesco), 6105 (Pix) or 6107 (PicPay). Required by the TechProcess platform for cross-border merchants. Required by the GlobalCollect platform when address is included in Seller. Required by the GlobalCollect platform for the creation of a Payout. |
|||
close
DescriptionZip code
Note: For payments with product 1503 the maximum length is not 10 but 8. Depends on:Required by the GlobalCollect platform for Direct Debit UK (705) except when a token has been included in the request that includes this value.
Required by the GlobalCollect platform for payments with product 9000 (AfterPay Installments) or 9001 (AfterPay Invoice). Required by the WOPA platform for payments with product 6101 (Banco do Brazil), 6102 (Itaú), 6103 (Banrisul), 6104 (Bradesco), 6105 (Pix) or 6107 (PicPay). Required by the TechProcess platform for cross-border merchants. |
|||
close
DescriptionThe last digits of the account number
|
|||
close
DescriptionThe name of the bank
|
|||
close
DescriptionThe country of the clearing house
|
|||
close
DescriptionThe ID number of the account holder
|
|||
close
DescriptionSofort (payment product 836) specific details
|
|||
close
DescriptionIndicates if SofortBank could estabilish if the transaction could successfully be processed.
|
|||
close
DescriptionPayPal (payment product 840) specific details
|
|||
close
DescriptionObject containing the billing address details of the customer
|
|||
close
DescriptionAdditional address information. The additionalInfo is truncated after 10 characters for payments, refunds or payouts that are processed by the WL Online Payment Acceptance platform
|
|||
close
DescriptionCity
Note: For payments with product 1503 the maximum length is not 40 but 20. Depends on:Required by the GlobalCollect platform for Invoice payments (201)
Required by the GlobalCollect platform for Direct Debit UK (705) except when a token has been included in the request that includes this value Required by the GlobalCollect platform for payments with product 9000 (AfterPay Installments) or 9001 (AfterPay Invoice). Required by the WOPA platform for payments with product 6101 (Banco do Brasil), 6102 (Itaú), 6103 (Banrisul), 6104 (Bradesco), 6105 (Pix) or 6107 (PicPay). Required by the TechProcess platform for cross-border merchants. Required by the GlobalCollect platform when address is included in Seller. Required by the GlobalCollect platform for the creation of a Payout. |
|||
close
DescriptionISO 3166-1 alpha-2 country code
Depends on:Required by the GlobalCollect platform.
Required by the TechProcess platform. |
|||
close
DescriptionHouse number. The houseNumber is truncated after 10 characters for payments, refunds or payouts that are processed by the WL Online Payment Acceptance platform
Depends on:Required when address is included in Seller.
Required for 6101 (Banco do Brasil), 6102 (Itaú), 6103 (Banrisul), 6104 (Bradesco), 6105 (Pix) and 6107 (PicPay). |
|||
close
DescriptionFull name of the state or province
Depends on:Required by the TechProcess platform for cross-border merchants.
|
|||
close
DescriptionISO 3166-2 alpha-3 state code
Notes:
Depends on:Required for payments with paymentProductId 1503 (Boleto), 6101 (Banco do Brasil), 6102 (Itaú), 6103 (Banrisul), 6104 (Bradesco), 6105 (Pix) or 6107 (PicPay).
|
|||
close
DescriptionStreetname
Depends on:Required by the GlobalCollect platform for Invoice payments (201)
Required by the GlobalCollect platform for Direct Debit UK (705), except when a token has been included in the request that includes this value. Required by the GlobalCollect platform for payments with product 9000 (AfterPay Installments) or 9001 (AfterPay Invoice). Required by the WOPA platform for payments with product 6101 (Banco do Brasil), 6102 (Itaú), 6103 (Banrisul), 6104 (Bradesco), 6105 (Pix) or 6107 (PicPay). Required by the TechProcess platform for cross-border merchants. Required by the GlobalCollect platform when address is included in Seller. Required by the GlobalCollect platform for the creation of a Payout. |
|||
close
DescriptionZip code
Note: For payments with product 1503 the maximum length is not 10 but 8. Depends on:Required by the GlobalCollect platform for Direct Debit UK (705) except when a token has been included in the request that includes this value.
Required by the GlobalCollect platform for payments with product 9000 (AfterPay Installments) or 9001 (AfterPay Invoice). Required by the WOPA platform for payments with product 6101 (Banco do Brazil), 6102 (Itaú), 6103 (Banrisul), 6104 (Bradesco), 6105 (Pix) or 6107 (PicPay). Required by the TechProcess platform for cross-border merchants. |
|||
close
DescriptionObject containing the details of the PayPal account
|
|||
close
DescriptionUsername with which the PayPal account holder has registered at PayPal
|
|||
close
DescriptionIdentification of the PayPal recurring billing agreement
|
|||
close
DescriptionName of the company in case the PayPal account is owned by a business
|
|||
close
DescriptionThe phone number of the PayPal account holder
|
|||
close
DescriptionCountry where the PayPal account is located
|
|||
close
DescriptionStatus of the PayPal account.
Possible values are:
|
|||
close
DescriptionStatus of the customer's shipping address as registered by PayPal
Possible values are:
|
|||
close
DescriptionFirst name of the PayPal account holder
|
|||
close
DescriptionThe unique identifier of a PayPal account and will never change in the life cycle of a PayPal account
|
|||
close
DescriptionSurname of the PayPal account holder
|
|||
close
DescriptionAdditional address information. The additionalInfo is truncated after 10 characters for payments, refunds or payouts that are processed by the WL Online Payment Acceptance platform
|
|||
close
DescriptionCity
Note: For payments with product 1503 the maximum length is not 40 but 20. Depends on:Required by the GlobalCollect platform for Invoice payments (201)
Required by the GlobalCollect platform for Direct Debit UK (705) except when a token has been included in the request that includes this value Required by the GlobalCollect platform for payments with product 9000 (AfterPay Installments) or 9001 (AfterPay Invoice). Required by the WOPA platform for payments with product 6101 (Banco do Brasil), 6102 (Itaú), 6103 (Banrisul), 6104 (Bradesco), 6105 (Pix) or 6107 (PicPay). Required by the TechProcess platform for cross-border merchants. Required by the GlobalCollect platform when address is included in Seller. Required by the GlobalCollect platform for the creation of a Payout. |
|||
close
DescriptionISO 3166-1 alpha-2 country code
Depends on:Required by the GlobalCollect platform.
Required by the TechProcess platform. |
|||
close
DescriptionHouse number. The houseNumber is truncated after 10 characters for payments, refunds or payouts that are processed by the WL Online Payment Acceptance platform
Depends on:Required when address is included in Seller.
Required for 6101 (Banco do Brasil), 6102 (Itaú), 6103 (Banrisul), 6104 (Bradesco), 6105 (Pix) and 6107 (PicPay). |
|||
close
DescriptionFull name of the state or province
Depends on:Required by the TechProcess platform for cross-border merchants.
|
|||
close
DescriptionISO 3166-2 alpha-3 state code
Notes:
Depends on:Required for payments with paymentProductId 1503 (Boleto), 6101 (Banco do Brasil), 6102 (Itaú), 6103 (Banrisul), 6104 (Bradesco), 6105 (Pix) or 6107 (PicPay).
|
|||
close
DescriptionStreetname
Depends on:Required by the GlobalCollect platform for Invoice payments (201)
Required by the GlobalCollect platform for Direct Debit UK (705), except when a token has been included in the request that includes this value. Required by the GlobalCollect platform for payments with product 9000 (AfterPay Installments) or 9001 (AfterPay Invoice). Required by the WOPA platform for payments with product 6101 (Banco do Brasil), 6102 (Itaú), 6103 (Banrisul), 6104 (Bradesco), 6105 (Pix) or 6107 (PicPay). Required by the TechProcess platform for cross-border merchants. Required by the GlobalCollect platform when address is included in Seller. Required by the GlobalCollect platform for the creation of a Payout. |
|||
close
DescriptionZip code
Note: For payments with product 1503 the maximum length is not 10 but 8. Depends on:Required by the GlobalCollect platform for Direct Debit UK (705) except when a token has been included in the request that includes this value.
Required by the GlobalCollect platform for payments with product 9000 (AfterPay Installments) or 9001 (AfterPay Invoice). Required by the WOPA platform for payments with product 6101 (Banco do Brazil), 6102 (Itaú), 6103 (Banrisul), 6104 (Bradesco), 6105 (Pix) or 6107 (PicPay). Required by the TechProcess platform for cross-border merchants. |
|||
close
DescriptionProtection Eligibility data of the PayPal customer
|
|||
close
DescriptionPossible values:
|
|||
close
DescriptionPossible values:
|
|||
close
DescriptionPayment product identifier
Please see payment products for a full overview of possible values. |
|||
close
DescriptionID of the token. This property is populated when the payment was done with a token or when the payment was tokenized.
|
|||
close
DescriptionObject containing the SEPA direct debit details
|
|||
close
DescriptionThis object contains the results of the Cybersource Decision Manager assessment. Cybersource is a fraud detection tool leveraging data networks, configurable rules, intelligence, and device fingerprinting to identify risky transactions.
|
|||
close
DescriptionName of the clause within the applied policy that was triggered during the evaluation of this transaction.
|
|||
close
DescriptionResult of the Cybersource Decision Manager check. This contains the normalized fraud score from a scale of 0 to 100. A higher score indicates an increased risk of fraud.
|
|||
close
DescriptionName of the policy that was applied during the evaluation of this transaction.
|
|||
close
DescriptionList of one or more reason codes.
|
|||
close
DescriptionResults from the fraud prevention check. Possible values are:
|
|||
close
DescriptionObject containing device fingerprinting details from InAuth
|
|||
close
DescriptionThe type of device used by the customer. Example values:
|
|||
close
DescriptionThis is the device fingerprint value. Based on the amount of data that the device fingerprint collector script was able to collect, this will be a proxy ID for the device used by the customer.
|
|||
close
DescriptionThe score calculated on the basis of Anomalies, Velocity, Location, Integrity, List-Based, and Device Reputation. Range of the score is between 0 and 100. A lower value is better.
|
|||
close
DescriptionThe true IP address as determined by inAuth. This might be different from the IP address that you are seeing on your side due to the proxy piercing technology deployed by inAuth.
|
|||
close
DescriptionThe country of the customer based on the location of the True IP Address determined by inAuth.
|
|||
close
DescriptionThis object contains the results of Microsoft Fraud Protection risk assessment. Microsoft collects transaction data points and uses Adaptive AI that continuously learns to protect you against payment fraud, and the device fingerprinting details from the Microsoft Device Fingerprinting service.
|
|||
close
DescriptionName of the clause within the applied policy that was triggered during the evaluation of this transaction.
|
|||
close
DescriptionThe country of the customer determined by Microsoft Device Fingerprinting.
|
|||
close
DescriptionThis is the device fingerprint value. Based on the amount of data that the device fingerprint collector script was able to collect, this will be a proxy ID for the device used by the customer.
|
|||
close
DescriptionResult of the Microsoft Fraud Protection check. This contains the normalized fraud score from a scale of 0 to 100. A higher score indicates an increased risk of fraud.
|
|||
close
DescriptionName of the policy that was applied on during the evaluation of this transaction.
|
|||
close
DescriptionList of one or more reason codes.
|
|||
close
DescriptionThe true IP address as determined by Microsoft Device Fingerprinting.
|
|||
close
DescriptionThe type of device used by the customer.
|
|||
close
DescriptionOutput that is SEPA Direct Debit specific (i.e. the used mandate)
|
|||
close
DescriptionUnique reference to a Mandate
|
|||
close
DescriptionPayment product identifier
Please see payment products for a full overview of possible values. |
|||
close
DescriptionID of the token. This property is populated for the GlobalCollect payment platform when the payment was done with a token or when the payment was tokenized.
|
|||
close
DescriptionPayment method identifier used by the our payment engine with the following possible values:
|
|||
close
DescriptionObject that holds all reference properties that are linked to this transaction
|
|||
close
DescriptionYour order ID for this transaction that is also returned in our report files
|
|||
close
DescriptionYour unique reference of the transaction that is also returned in our report files. This is almost always used for your reconciliation of our report files.
|
|||
close
DescriptionPayment Reference generated by WebCollect
|
|||
close
DescriptionProvides an additional means of reconciliation for Gateway merchants
|
|||
close
DescriptionProvides an additional means of reconciliation, this is the MerchantId used at the provider
|
|||
close
DescriptionProvides an additional means of reconciliation for Gateway merchants
|
|||
close
DescriptionWhen you did not supply a merchantReference for your payment, you need to fill this property with the reference of the original payment when you want to refund it
|
|||
close
DescriptionThe reason description given for the reversedAmount property.
|
|||
close
DescriptionCurrent high-level status of the payment in a human-readable form. Possible values are :
Please see Statuses for a full overview of possible values. |
|||
close
DescriptionThis object has the numeric representation of the current payment status, timestamp of last status change and performable action on the current payment resource.
In case of failed payments and negative scenarios, detailed error information is listed.
|
|||
close
DescriptionCustom object contains the set of errors
|
|||
close
DescriptionCategory the error belongs to. The category should give an indication of the type of error you are dealing with.
Possible values:
|
|||
close
DescriptionError code
|
|||
close
DescriptionHTTP status code for this error that can be used to determine the type of error
|
|||
close
DescriptionID of the error. This is a short human-readable message that briefly describes the error.
|
|||
close
DescriptionHuman-readable error message that is not meant to be relayed to customer as it might tip off people who are trying to commit fraud
|
|||
close
DescriptionReturned only if the error relates to a value that was missing or incorrect.
Contains a location path to the value as a JSonata query. Some common examples:
|
|||
close
DescriptionID of the request that can be used for debugging purposes
|
|||
close
DescriptionIndicates if the transaction has been authorized
|
|||
close
DescriptionFlag indicating if the payment can be cancelled
|
|||
close
DescriptionFlag indicating if the payment can be refunded
|
|||
close
DescriptionFlag indicating whether a rejected payment may be retried by the merchant without incurring a fee
|
|||
close
DescriptionThis is the raw response returned by the acquirer. This property contains unprocessed data directly returned by the acquirer. It's recommended for data analysis only due to its dynamic nature, which may undergo future changes.
|
|||
close
DescriptionName of the key or property
|
|||
close
DescriptionValue of the key or property
|
|||
close
DescriptionHighlevel status of the payment, payout or refund with the following possible values:
Please see Statuses for a full overview of possible values. |
|||
close
DescriptionNumeric status code of the legacy API. It is returned to ease the migration from the legacy APIs to Worldline Connect. You should not write new business logic based on this property as it will be deprecated in a future version of the API. The value can also be found in the GlobalCollect Payment Console, in the Ogone BackOffice and in report files.
|
|||
close
DescriptionDate and time of payment
Format: YYYYMMDDHH24MISS |
|||
close
DescriptionThe 3D Secure status, with the following possible values:
|
|||
close
Deprecated:
Use cardPaymentMethodSpecificOutput instead
DescriptionObject containing additional payment method specific details
Deprecated: this property does not support different outputs for payment methods other than cards. Please use cardPaymentMethodSpecificOutput instead.
|
|||
close
Deprecated
DescriptionResult of the authorization reversal request
Possible values are:
|
|||
Property | Type | Required | Details |
Response example
This scenario you will probably use the most
-
{ "payment" : { "id" : "000000891500000237080000200001", "paymentOutput" : { "amountOfMoney" : { "amount" : 2890, "currencyCode" : "EUR" }, "references" : { "paymentReference" : "0" }, "paymentMethod" : "card", "cardPaymentMethodSpecificOutput" : { "paymentProductId" : 1, "authorisationCode" : "123456", "card" : { "cardNumber" : "************7977", "expiryDate" : "1299" }, "fraudResults" : { "avsResult" : "0", "cvvResult" : "M", "fraudServiceResult" : "no-advice" }, "threeDSecureResults" : { "authenticationAmount" : { "currencyCode" : "EUR", "amount" : 2890 } } } }, "status" : "CAPTURE_REQUESTED", "statusOutput" : { "isCancellable" : true, "statusCode" : 800, "statusCodeChangeDateTime" : "20140627140735", "isAuthorized" : true } } }
Response 400 - Bad requestErrorResponse
Properties
|
|||
Property | Type | Required | Details |
---|---|---|---|
errorId | string | yes | read close |
close
DescriptionUnique reference, for debugging purposes, of this error response
|
|||
array of object | yes | read close | |
close
DescriptionList of one or more errors
|
|||
close
DescriptionCategory the error belongs to. The category should give an indication of the type of error you are dealing with.
Possible values:
|
|||
close
DescriptionError code
|
|||
close
DescriptionHTTP status code for this error that can be used to determine the type of error
|
|||
close
DescriptionID of the error. This is a short human-readable message that briefly describes the error.
|
|||
close
DescriptionHuman-readable error message that is not meant to be relayed to customer as it might tip off people who are trying to commit fraud
|
|||
close
DescriptionReturned only if the error relates to a value that was missing or incorrect.
Contains a location path to the value as a JSonata query. Some common examples:
|
|||
close
DescriptionID of the request that can be used for debugging purposes
|
|||
Property | Type | Required | Details |
Response example
This scenario you will probably use the most
-
{ "errorId" : "15eabcd5-30b3-479b-ae03-67bb351c07e6-00000092", "errors" : [ { "code" : "20000000", "propertyName" : "bankAccountBban.accountNumber", "message" : "PARAMETER_NOT_FOUND_IN_REQUEST" } ] }
Response 402 - Payment requiredErrorResponse
Properties
|
|||
Property | Type | Required | Details |
---|---|---|---|
errorId | string | yes | read close |
close
DescriptionUnique reference, for debugging purposes, of this error response
|
|||
array of object | yes | read close | |
close
DescriptionList of one or more errors
|
|||
close
DescriptionCategory the error belongs to. The category should give an indication of the type of error you are dealing with.
Possible values:
|
|||
close
DescriptionError code
|
|||
close
DescriptionHTTP status code for this error that can be used to determine the type of error
|
|||
close
DescriptionID of the error. This is a short human-readable message that briefly describes the error.
|
|||
close
DescriptionHuman-readable error message that is not meant to be relayed to customer as it might tip off people who are trying to commit fraud
|
|||
close
DescriptionReturned only if the error relates to a value that was missing or incorrect.
Contains a location path to the value as a JSonata query. Some common examples:
|
|||
close
DescriptionID of the request that can be used for debugging purposes
|
|||
Property | Type | Required | Details |
Response example
This scenario you will probably use the most
-
{ "errorId" : "1105db54-9c91-4a97-baa7-3c4182458047", "errors" : [ { "code" : "410110", "requestId" : "3927859", "message" : "UNKNOWN ORDER OR NOT PENDING" } ] }
Response 404 - Not foundErrorResponse
The payment you are trying to approve can't be found.
Properties
|
|||
Property | Type | Required | Details |
---|---|---|---|
errorId | string | yes | read close |
close
DescriptionUnique reference, for debugging purposes, of this error response
|
|||
array of object | yes | read close | |
close
DescriptionList of one or more errors
|
|||
close
DescriptionCategory the error belongs to. The category should give an indication of the type of error you are dealing with.
Possible values:
|
|||
close
DescriptionError code
|
|||
close
DescriptionHTTP status code for this error that can be used to determine the type of error
|
|||
close
DescriptionID of the error. This is a short human-readable message that briefly describes the error.
|
|||
close
DescriptionHuman-readable error message that is not meant to be relayed to customer as it might tip off people who are trying to commit fraud
|
|||
close
DescriptionReturned only if the error relates to a value that was missing or incorrect.
Contains a location path to the value as a JSonata query. Some common examples:
|
|||
close
DescriptionID of the request that can be used for debugging purposes
|
|||
Property | Type | Required | Details |
Response example
This scenario you will probably use the most
-
{ "errorId" : "657b10da-d2f9-4088-a948-bf190ef516b1-00000213", "errors" : [ { "code" : "300240", "message" : "GET_ORDERSTATUS_ORDER_NOT_FOUND" } ] }