Create refund
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
You can refund any transaction by just calling this API. The system will automatically select the most appropriate means to refund the transaction based on the payment product that was used for the payment and the currency and the country of the refund request.
Depending on the payment product of the payment you will need to supply refund specific details on where the money should be refunded to or not. You always have the option to refund just a portion of the payment amount. It is also possible to submit multiple refund requests on one payment as long as the total amount to be refunded does not exceed the total amount that was paid.
PayloadRefundRequest
Properties
|
|||
Property | Type | Required | Details |
---|---|---|---|
object | no | read close | |
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
|
|||
object | no | read close | |
close
DescriptionObject containing the specific input details for a bank refund
|
|||
close
DescriptionObject that holds the Basic Bank Account Number (BBAN) data
|
|||
close
DescriptionName of the account holder
|
|||
close
DescriptionBank account number
|
|||
close
DescriptionCity of the bank to refund to
|
|||
close
DescriptionBank code
|
|||
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
|
|||
close
DescriptionEvery Russian has three names: a first name, a patronymic, and a surname. The second name is a patronymic. Russian patronymic is a name derived from the father's first name by adding -ович/-евич (son of) for male, or -овна/-евна (daughter of) for females.
|
|||
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. The BIC contains 8 or 11 positions: the first 4 contain the bank code, followed by the country code and location code.
|
|||
close
DescriptionObject that holds the International Bank Account Number (IBAN) data
|
|||
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
DescriptionISO 3166-1 alpha-2 country code of the country where money will be refunded to
|
|||
object | no | read close | |
close
DescriptionAdditional address information
|
|||
close
DescriptionCity
Depends on:Required by the TechProcess platform for cross-border merchants.
|
|||
close
DescriptionISO 3166-1 alpha-2 country code
Depends on:Required by the TechProcess platform for cross-border merchants.
|
|||
close
DescriptionHouse number
|
|||
close
DescriptionObject that holds the name elements
Depends on:Required by the TechProcess platform for cross-border merchants.
|
|||
close
DescriptionGiven name(s) or first name(s) of the customer. The '+' character is not allowed in this property for transactions that are processed by TechProcess Payment Platform.
Depends on:Required by the GlobalCollect platform for payments with Trustly (paymentProductId 806), AfterPay Installments (paymentProductId 9000), AfterPay Invoice (paymentProductId 9001), BC Card (paymentProductId 8590), Hana Card (paymentProductId 8591), Hyundai Card (paymentProductId 8592), KB Card (paymentProductId 8593), Lotte Card (paymentProductId 8594), NH Card (paymentProductId 8595), Samsung Card (paymentProductId 8596), Shinhan Card (paymentProductId 8597).
Required for merchants that use Merchant Category Codes (MCC) V4829, V6012, M4829, V6051, M6540, 7995. Required by the WOPA platform for payments with product Banco do Brasil (paymentProductId 6101), Itaú (paymentProductId 6102), Banrisul (paymentProductId 6103), Bradesco (paymentProductId 6104), Pix (paymentProductId 6105), PicPay (paymentProductId 6107) or SPEI (paymentProductId 6501). For payments made in Brazil, this property is only required when the property order.customer.fiscalNumber is Personal (CPF) - 11 digits. Required by the TechProcess platform for payments. |
|||
close
DescriptionSurname(s) or last name(s) of the customer. The surname is truncated after 25 characters, with the limit being applied after surnamePrefix is prepended, for payments, refunds or payouts that are processed by the WL Online Payment Acceptance platform The '+' character is not allowed in this property for transactions that are processed by TechProcess Payment Platform.
Depends on:Required by the GlobalCollect platform for payments with Trustly (paymentProductId 806), AfterPay Installments (paymentProductId 9000), AfterPay Invoice (paymentProductId 9001), BC Card (paymentProductId 8590), Hana Card (paymentProductId 8591), Hyundai Card (paymentProductId 8592), KB Card (paymentProductId 8593), Lotte Card (paymentProductId 8594), NH Card (paymentProductId 8595), Samsung Card (paymentProductId 8596), Shinhan Card (paymentProductId 8597).
Required for the creation of a Payout. Required for merchants that use Merchant Category Codes (MCC) V4829, V6012, M4829, V6051, M6540, 7995. Required by the WOPA platform for payments with product Banco do Brasil (paymentProductId 6101), Itaú (paymentProductId 6102), Banrisul (paymentProductId 6103), Bradesco (paymentProductId 6104), Pix (paymentProductId 6105), PicPay (paymentProductId 6107) or SPEI (paymentProductId 6501). For payments made in Brazil, this property is only required when the property order.customer.fiscalNumber is Personal (CPF) - 11 digits. Required for the creation of a Payout. Required by the Ogone platform for the creation of a Payout. Required by the TechProcess platform for the creation of a payment. |
|||
close
DescriptionMiddle name - In between first name and surname - of the customer. The '+' character is not allowed in this property for transactions that are processed by TechProcess Payment Platform.
|
|||
close
DescriptionTitle of customer
Depends on:Required for payments with product 9000 (AfterPay Installments) or 9001 (AfterPay Invoice) in Austria (AT), Belgium (BE), Germany (DE), the Netherlands (NL) and Switzerland (CH).
|
|||
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)
|
|||
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 TechProcess platform for cross-border merchants. |
|||
close
DescriptionZip code
Depends on:Required by the GlobalCollect platform for Required for Direct Debit UK (705), except when a token has been included in the request that includes this value.
Required by the TechProcess platform for cross-border merchants. |
|||
close
DescriptionThe date of incorporation is the specific date when the company was registered with the relevant authority.
Format: YYYYMMDD Depends on:Required by the TechProcess platform for cross-border payments when the property order.customer.isCompany is set to true.
|
|||
close
DescriptionName of company, as a customer
Depends on:Required by the WOPA platform for payments when the property order.customer.fiscalNumber is set to:
|
|||
close
DescriptionLocal VAT number of the company
Depends on:One of the following properties is required for merchants that use Merchant Category Codes (MCC)
V4829, V6012, M4829, V6051, M6540, 7995:
|
|||
close
DescriptionObject containing contact details like email address and phone number
|
|||
close
DescriptionEmail address of the customer
|
|||
close
DescriptionPreference for the type of email message markup
|
|||
close
DescriptionThe fiscal registration number of the customer or the tax registration number of the company in case of a business customer. Please find below specifics per country:
|
|||
refundDate | string (8) | no | read close |
close
DescriptionRefund date
Format: YYYYMMDD |
|||
object | no | read close | |
close
DescriptionObject that holds all reference properties that are linked to this refund
|
|||
close
DescriptionNote that the maximum length of this field for transactions processed on the GlobalCollect platform is 30. Your 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. |
|||
Property | Type | Required | Details |
Request example
This scenario you will probably use the most
-
var amountOfMoney = new AmountOfMoney(); amountOfMoney.Amount = 1L; amountOfMoney.CurrencyCode = "EUR"; var bankAccountIban = new BankAccountIban(); bankAccountIban.Iban = "NL53INGB0000000036"; var bankRefundMethodSpecificInput = new BankRefundMethodSpecificInput(); bankRefundMethodSpecificInput.BankAccountIban = bankAccountIban; var name = new PersonalName(); name.Surname = "Coyote"; var address = new AddressPersonal(); address.CountryCode = "US"; address.Name = name; var contactDetails = new ContactDetailsBase(); contactDetails.EmailAddress = "wile.e.coyote@acmelabs.com"; contactDetails.EmailMessageType = "html"; var customer = new RefundCustomer(); customer.Address = address; customer.ContactDetails = contactDetails; var refundReferences = new RefundReferences(); refundReferences.MerchantReference = "AcmeOrder0001"; var body = new RefundRequest(); body.AmountOfMoney = amountOfMoney; body.BankRefundMethodSpecificInput = bankRefundMethodSpecificInput; body.Customer = customer; body.RefundDate = "20140306"; body.RefundReferences = refundReferences; try { var response = await client.V1.WithNewMerchant("merchantId").Payments.Refund("paymentId", body); } catch (DeclinedRefundException e) { HandleDeclinedRefund(e.RefundResult); } catch (ApiException e) { HandleErrorResponse(e.ErrorId, e.Errors); }
Responses
Please find below an overview of the possible responses.
Response 201 - CreatedRefundResponse
The refund was successfully created.
In the HTTP header the location is provided of the created refund object so you can easily query its status, by simply performing a GET on the URI provided in this header.
Properties
|
|||
Property | Type | Required | Details |
---|---|---|---|
id | string | no | read close |
close
DescriptionOur unique refund transaction identifier
|
|||
object | no | read close | |
close
DescriptionInformation of the refund resource such as amount, currency, nature of the refund.
|
|||
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 paid
|
|||
close
DescriptionObject containing specific bank refund details
|
|||
close
DescriptionRefund product identifier
Please see refund products for a full overview of possible values. |
|||
close
DescriptionTotal paid amount (in cents and always with 2 decimals)
|
|||
close
DescriptionTotal refunded amount (in cents and always with 2 decimals)
|
|||
close
DescriptionObject containing specific card refund 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
DescriptionRefund product identifier
Please see refund products for a full overview of possible values. |
|||
close
DescriptionTotal paid amount (in cents and always with 2 decimals)
|
|||
close
DescriptionTotal refunded amount (in cents and always with 2 decimals)
|
|||
close
DescriptionObject containing specific cash refund details
|
|||
close
DescriptionRefund product identifier
Please see refund products for a full overview of possible values. |
|||
close
DescriptionTotal paid amount (in cents and always with 2 decimals)
|
|||
close
DescriptionTotal refunded amount (in cents and always with 2 decimals)
|
|||
close
DescriptionObject containing specific e-invoice refund details
|
|||
close
DescriptionRefund product identifier
Please see refund products for a full overview of possible values. |
|||
close
DescriptionTotal paid amount (in cents and always with 2 decimals)
|
|||
close
DescriptionTotal refunded amount (in cents and always with 2 decimals)
|
|||
close
DescriptionObject containing specific eWallet refund details
|
|||
close
DescriptionPayPal (payment product 840) specific details
|
|||
close
DescriptionObject containing the PayPal account details
|
|||
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
DescriptionThe unique identifier of a PayPal account and will never change in the life cycle of a PayPal account
|
|||
close
DescriptionRefund product identifier
Please see refund products for a full overview of possible values. |
|||
close
DescriptionTotal paid amount (in cents and always with 2 decimals)
|
|||
close
DescriptionTotal refunded amount (in cents and always with 2 decimals)
|
|||
close
DescriptionObject containing specific mobile refund details
|
|||
close
DescriptionThe network that was used for the refund. The string that represents the network is identical to the strings that the payment product vendors use in their documentation.
For instance: "Visa" for Apple Pay, and "VISA" for Google Pay.
|
|||
close
DescriptionRefund product identifier
Please see refund products for a full overview of possible values. |
|||
close
DescriptionTotal paid amount (in cents and always with 2 decimals)
|
|||
close
DescriptionTotal refunded amount (in cents and always with 2 decimals)
|
|||
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 refund
|
|||
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
|
|||
status | enum | no | read close |
close
DescriptionCurrent high-level status of the refund in a human-readable form. Possible values are:
Please see Statuses for a full overview of possible values. |
|||
object | no | read close | |
close
DescriptionThis object has the numeric representation of the current refund status, timestamp of last status change and performable action on the current refund resource.
In case of a rejected refund, 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
DescriptionFlag indicating if the payment can be cancelled
|
|||
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 |
|||
Property | Type | Required | Details |
Response example
This scenario you will probably use the most
-
{ "id" : "00000085001000006995000-300001", "refundOutput" : { "amountOfMoney" : { "amount" : 1, "currencyCode" : "EUR" }, "references" : { "merchantReference" : "AcmeOrder0001", "paymentReference" : "0" }, "paymentMethod" : "card", "cardRefundMethodSpecificOutput" : { "totalAmountPaid" : 2890, "totalAmountRefunded" : 0 } }, "status" : "PENDING_APPROVAL", "statusOutput" : { "isCancellable" : true, "statusCode" : 800, "statusCodeChangeDateTime" : "20140625154922" } }
Response 400 - Bad requestRefundErrorResponse
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
|
|||
object | no | read close | |
close
DescriptionObject that contains details on the created refund in case one has been created
|
|||
close
DescriptionOur unique refund 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 paid
|
|||
close
DescriptionObject containing specific bank refund details
|
|||
close
DescriptionRefund product identifier
Please see refund products for a full overview of possible values. |
|||
close
DescriptionTotal paid amount (in cents and always with 2 decimals)
|
|||
close
DescriptionTotal refunded amount (in cents and always with 2 decimals)
|
|||
close
DescriptionObject containing specific card refund 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
DescriptionRefund product identifier
Please see refund products for a full overview of possible values. |
|||
close
DescriptionTotal paid amount (in cents and always with 2 decimals)
|
|||
close
DescriptionTotal refunded amount (in cents and always with 2 decimals)
|
|||
close
DescriptionObject containing specific cash refund details
|
|||
close
DescriptionRefund product identifier
Please see refund products for a full overview of possible values. |
|||
close
DescriptionTotal paid amount (in cents and always with 2 decimals)
|
|||
close
DescriptionTotal refunded amount (in cents and always with 2 decimals)
|
|||
close
DescriptionObject containing specific e-invoice refund details
|
|||
close
DescriptionRefund product identifier
Please see refund products for a full overview of possible values. |
|||
close
DescriptionTotal paid amount (in cents and always with 2 decimals)
|
|||
close
DescriptionTotal refunded amount (in cents and always with 2 decimals)
|
|||
close
DescriptionObject containing specific eWallet refund details
|
|||
close
DescriptionPayPal (payment product 840) specific details
|
|||
close
DescriptionObject containing the PayPal account details
|
|||
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
DescriptionThe unique identifier of a PayPal account and will never change in the life cycle of a PayPal account
|
|||
close
DescriptionRefund product identifier
Please see refund products for a full overview of possible values. |
|||
close
DescriptionTotal paid amount (in cents and always with 2 decimals)
|
|||
close
DescriptionTotal refunded amount (in cents and always with 2 decimals)
|
|||
close
DescriptionObject containing specific mobile refund details
|
|||
close
DescriptionThe network that was used for the refund. The string that represents the network is identical to the strings that the payment product vendors use in their documentation.
For instance: "Visa" for Apple Pay, and "VISA" for Google Pay.
|
|||
close
DescriptionRefund product identifier
Please see refund products for a full overview of possible values. |
|||
close
DescriptionTotal paid amount (in cents and always with 2 decimals)
|
|||
close
DescriptionTotal refunded amount (in cents and always with 2 decimals)
|
|||
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 refund
|
|||
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
DescriptionCurrent high-level status of the refund 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 refund status, timestamp of last status change and performable action on the current refund resource.
In case of a rejected refund, 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
DescriptionFlag indicating if the payment can be cancelled
|
|||
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 |
|||
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" : "bankRefundMethodSpecificInput.bankAccountBban.accountNumber", "message" : "PARAMETER_NOT_FOUND_IN_REQUEST" } ] }
Response 404 - Not foundRefundErrorResponse
The most common cause for this response id that the payment was not in a cancelable state.
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
|
|||
object | no | read close | |
close
DescriptionObject that contains details on the created refund in case one has been created
|
|||
close
DescriptionOur unique refund 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 paid
|
|||
close
DescriptionObject containing specific bank refund details
|
|||
close
DescriptionRefund product identifier
Please see refund products for a full overview of possible values. |
|||
close
DescriptionTotal paid amount (in cents and always with 2 decimals)
|
|||
close
DescriptionTotal refunded amount (in cents and always with 2 decimals)
|
|||
close
DescriptionObject containing specific card refund 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
DescriptionRefund product identifier
Please see refund products for a full overview of possible values. |
|||
close
DescriptionTotal paid amount (in cents and always with 2 decimals)
|
|||
close
DescriptionTotal refunded amount (in cents and always with 2 decimals)
|
|||
close
DescriptionObject containing specific cash refund details
|
|||
close
DescriptionRefund product identifier
Please see refund products for a full overview of possible values. |
|||
close
DescriptionTotal paid amount (in cents and always with 2 decimals)
|
|||
close
DescriptionTotal refunded amount (in cents and always with 2 decimals)
|
|||
close
DescriptionObject containing specific e-invoice refund details
|
|||
close
DescriptionRefund product identifier
Please see refund products for a full overview of possible values. |
|||
close
DescriptionTotal paid amount (in cents and always with 2 decimals)
|
|||
close
DescriptionTotal refunded amount (in cents and always with 2 decimals)
|
|||
close
DescriptionObject containing specific eWallet refund details
|
|||
close
DescriptionPayPal (payment product 840) specific details
|
|||
close
DescriptionObject containing the PayPal account details
|
|||
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
DescriptionThe unique identifier of a PayPal account and will never change in the life cycle of a PayPal account
|
|||
close
DescriptionRefund product identifier
Please see refund products for a full overview of possible values. |
|||
close
DescriptionTotal paid amount (in cents and always with 2 decimals)
|
|||
close
DescriptionTotal refunded amount (in cents and always with 2 decimals)
|
|||
close
DescriptionObject containing specific mobile refund details
|
|||
close
DescriptionThe network that was used for the refund. The string that represents the network is identical to the strings that the payment product vendors use in their documentation.
For instance: "Visa" for Apple Pay, and "VISA" for Google Pay.
|
|||
close
DescriptionRefund product identifier
Please see refund products for a full overview of possible values. |
|||
close
DescriptionTotal paid amount (in cents and always with 2 decimals)
|
|||
close
DescriptionTotal refunded amount (in cents and always with 2 decimals)
|
|||
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 refund
|
|||
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
DescriptionCurrent high-level status of the refund 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 refund status, timestamp of last status change and performable action on the current refund resource.
In case of a rejected refund, 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
DescriptionFlag indicating if the payment can be cancelled
|
|||
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 |
|||
Property | Type | Required | Details |
Response example
This scenario you will probably use the most
-
{ "errorId" : "27ba5f42-e750-4cba-a3ed-9ab90067c849-0000917a", "errors" : [ { "code" : "300240", "requestId" : "142727", "message" : "GET_ORDERSTATUS ORDER NOT FOUND" } ] }