Oney BNPL

At Oney, we have a different, unique vision of financial services and payment solutions: more modern, more responsible and more human. As a partner in the transformation of commerce, with our thousands of retail partners, we give everyone the power to improve their daily lives and consume better.

Source: https://www.oney.com/

Features

Integration type

Redirection

Tokenization

Yes

Payment Flow

1-step payment flow : Capture (direct debit)

2-step payment flow : Authorization + Capture

3-step payment flow : Pending Authorization + Authorization + Capture

Additional features

Information request and CIT

MIT

Server-to-server

How to test?

info

Oney finances only French B2C customers. Your Create Session call must contains an order.customer node, valued with French customer data. If order.customer.company is valued, your payment will be refused.

Test Cards

Credentials	SUCCESS	PENDING	REFUSED
Card number	4970 1064 3474 0000	4970 1064 3474 0000	4970 1064 3474 0000
Customer email address	[email protected]	[email protected]	[email protected]
Expiry date	any future month and year	any future month and year	any future month and year
CVC	any 3 random numbers	any 3 random numbers	any 3 random numbers

info

As you can see on the table above, order.customer.billing_adress.email can be valued with specific email address to test different behaviours.

Data Mapping & Mandatory Fields

Below is the mapping between your Create Session request and the fields expected by this payment method.

Purse Session field	Mandatory
amount	Yes
order.redirection	Yes
order.reference	Yes
order.amount	Yes
order.currency_code	Yes
customer.reference	Yes
customer.type_code	No
customer.company_name	No
customer.gender_code	No
customer.first_name	No
customer.last_name	No
customer.birthdate	No
customer.locale_code	Yes
customer.billing_address.delivery_point_name	No
customer.billing_address.address_lines	Yes
customer.billing_address.city	Yes
customer.billing_address.postal_code	Yes
customer.billing_address.country_code	Yes
customer.billing_address.email	Yes
customer.billing_address.phone	Yes
customer.billing_address.mobile_phone	Yes
customer.additional_attributes.national_identifier	No
shipments.delivery_type_code	Yes
shipments.delivery_quickness_code	Yes
shipments.estimated_delivery_date_time	Yes
shipments.shipping_address.delivery_point_name	Yes
shipments.shipping_address.gender_code	Yes
shipments.shipping_address.first_name	Yes
shipments.shipping_address.last_name	Yes
shipments.shipping_address.address_lines	Yes
shipments.shipping_address.city	Yes
shipments.shipping_address.postal_code	Yes
shipments.shipping_address.country_code	Yes
shipments.shipping_address.email	Yes
shipments.seller_name	Yes
shipments.seller_reference	Yes
shipments.item_lines.type_code	No
shipments.item_lines.sku_reference	Yes
shipments.item_lines.name	Yes
shipments.item_lines.quantity	Yes
shipments.item_lines.amount	Yes

Payment Labels

Label	Method	Payment type
oney	paylater	primary (payment by installments)

Actions

Action	Mandatory fields	Optional fields
APPLY	amount 0 currency_code EUR customer {"gender_code":"unknown","locale_code":"und","billing_address":{"address_lines":["line1","line2"]}} shipments [{"delivery_type_code":"user_delivery","delivery_quickness_code":"regular","shipping_address":{"address_lines":["line1","line2"]},"item_lines":[{"price":10,"quantity":1}]}]	-

Status

PSP status	State	Code	Description
11	ERROR	BAD_REQUEST	Failed to Cancel – the service is not available
14	ERROR	BAD_REQUEST	Technical error – the Order data could not be retrieved.
ERROR	ERROR	FAILED	The partner returned an error
ERR_01	ERROR	BAD_REQUEST	Field is required: Identify and correct the field then retry the call to the service.
ERR_02	ERROR	BAD_REQUEST	Field size is incorrect: Identify and correct the field then retry the call to the service.
ERR_03	ERROR	BAD_REQUEST	Field format is not valid: Identify and correct the field then retry the call to the service.
ERR_04
ERR_05
ERR_06
ERR_07	ERROR	BAD_REQUEST	An unexpected error occurred when trying to process the request. Please retry the call to the service.
ERR_09
ERR_10	ERROR	BAD_REQUEST	The order associated with the reference does not exist: The field purchase/external_reference
ERR_13	ERROR	BAD_REQUEST	The amount must be lower than or equal to amount initially saved. (Can occur for partial capture where Oney makes internally a refund au adjust the Authorized amount and match it to the requested capture amount. ie: if Authorized amount= 30€, capture amount= 29.10€ Oney will try refund of 0.90€ and it will fail.)
ERR_17	ERROR	BAD_REQUEST	The order status does not allow to process a cancellation request.
ERR_18	ERROR	BAD_REQUEST	Service is not available
ERR_19	ERROR	BAD_REQUEST	An error occurred when trying to process the request: Please retry the call to the service.
ERR_20	ERROR	BAD_REQUEST	The payment status does not allow cancellation.
ERR_23	ERROR	BAD_REQUEST	Field type is not compatible with parameter entries: Identify and correct the field then retry the call to the service.
ERR_25	ERROR	BAD_REQUEST	The required field “Code barre de fidélité” is not filled in. Only if the merchant is configured to use loyalty.
ERR_26	ERROR	BAD_REQUEST	An order already exists with the same references and creation date: The field purchase/external_reference.
ERR_29	ERROR	BAD_REQUEST	invalid business transaction code: Review the payment request and change the business transaction code by a valid one
ERR_30	ERROR	BAD_REQUEST	The order is canceled or is being canceled.
FUNDED	SUCCESS	SUCCEEDED	FUNDED : Transaction is completed
ABORTED	ERROR	EXPIRED_AUTHORIZATION	ABORTED : Payment in timeout
PENDING	WAITING	WAITING_PARTNER_RESPONSE	PENDING : Waiting for Oney acceptance
REFUSED	ERROR	REJECTED_BANK	REFUSED : Payment was refused
SUCCESS	SUCCESS	SUCCEEDED	Successfully
CANCELLED	SUCCESS	SUCCEEDED	CANCELLED : Payment has been cancelled
FAVORABLE	SUCCESS	SUCCEEDED	FAVORABLE : Oney accepts the payment
TO_BE_FUNDED	WAITING	WAITING_PARTNER_RESPONSE	TO_BE_FUNDED : Payment in progress and merchant is sending the items