Authorization Code in Credit Card Payments
Authorization Code in Credit Card Payments |
---|
For all payments made by Credit Card (CC), the authorization code obtained by Iberia in the process will be returned in the OrderViewRS at the time of payment.
This authorization code will be included in the OrderViewRS for the following messages:
OrderCreate: Payment with instant Purchase.
OrderChange: Deferred Payment.
OrderChange: Flight Change.
OrderChange: Ancillaries Postsale.
NOTE: Rest of OrderView as the payment process is not involved, no payment information is being returned.
The credit card payment method (PaymentCard
element) can have a total of three optional references: one for the installment information; another for the 3DS information; and one for the authorization code. The installment and 3DS functionality is not affected.
PaymentCard
information is referenced to the authorization code information, which is in the PaymentFormMetadata
.
The PaymentFormMetadata element will have a MetadataKey attribute with a unique key that can be referenced from the credit card payment form.
In NDC messages the authorization code will be returned in the:
/OrderViewRS/Response/Metadata/Other/OtherMetadata/PaymentFormMetadatas/PaymentFormMetadata/Text
In the Text field, you can receive:
Installment information is in the following format: “installments/#[number of installments]/#[interest rate charged]. Example of OrderViewRS: “installments/3/12” where, 3 is the number of installments, and 12 is the interest rate.
Authorization code in the following format: ‘'Authorization/[Code of Authorization]''. OrderViewRS example: ‘'Authorization/AQW45F''
<Payments>
<Payment>
<Type>CC</Type>
<Method>
<PaymentCard refs="this_is_the_key_of_the_authorization_code">
...
</PaymentCard>
...
</Payment>
</Payments>
<Metadata>
<Other>
<OtherMetadata>
<CurrencyMetadatas>
<CurrencyMetadata MetadataKey="EUR">
<Decimals>2</Decimals>
</CurrencyMetadata>
</CurrencyMetadatas>
</OtherMetadata>
<OtherMetadata>
<PaymentFormMetadatas>
<PaymentFormMetadata MetadataKey="KEY_QUOTAS"> --> (PaymentCard information)
<Text>installments/3</Text> --> (Payment in three installments)
</PaymentFormMetadata>
<PaymentFormMetadata MetadataKey="KEY_AUTHORIZATION_CODE_1"> --> (PaymentCard information)
<Text>Authorization/2XS56F</Text> --> (Authorization code)
</PaymentFormMetadata>
</PaymentFormMetadatas>
</OtherMetadata>
</Other>
</Metadata>
Therefore, and given that they are already being referenced for the 3DS and installments information, it would be as follows:
<PaymentCard refs="KEY_QUOTAS KEY_AUTHORIZATION_CODE_1">
Pay in installments without 3DS.<PaymentCard refs="KEY_3DS KEY_AUTHORIZATION_CODE_1">
Pay by 3DS without installments.<PaymentCard refs="KEY_AUTHORIZATION_CODE_1">
Pay without installments and without 3DS.
OrderViewRS - Payment Messages |
---|
Credit Card Payment with installments in On Hold Order example:
You can see in the RQ:
<PaymentCard refs=”KEY_QUOTAS”>
<PaymentFormMetadata MetadataKey=”KEY_QUOTAS”>
You can see in the RS:
<PaymentFormMetadata MetadataKey=”KEY_QUOTAS”>
<PaymentFormMetadata MetadataKey=”KEY_AUTHORIZATION_CODE_1”>
Credit Card Payment with 3DS in an OrderCreateRQ example:
You can see in the RQ:
<PaymentCard refs=”KEY_3DS”>
You can see in the RS:
<PaymentFormMetadata MetadataKey=”KEY_AUTHORIZATION_CODE_1”>
You can see in OrderRetrieve that there is no related information:
Credit Card Payment without 3DS and without installments in Ancillaries Post-Sale Order example:
You can see in the RQ any PaymentCard refs
You can see in the RS:
<PaymentFormMetadata MetadataKey=”KEY_AUTHORIZATION_CODE_1”>